This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GLIBC bug list on sourceware.org


On Sat, Oct 29, 2016 at 9:01 PM, Carlos O'Donell <carlos@redhat.com> wrote:
> On 10/20/2016 03:35 PM, Adhemerval Zanella wrote:
>> Hi all,
>>
>> As Joseph has pointed out earlier in IRC, sourceware.og just surpassed
>> 1000 registered bugs [1].  And this list only increases over time.
> ...
>> Any thoughts, ideas, advices?
>
> Do the work? :-)
>
> I created a 7day review query for bugzilla.
>
> Florian and I just fixed the -Os bug that came in.
>
> We just need to target the incoming bugs and drive them to conclusion.

In GCC, that is what I try to do; though the number of bugs reported
are high and many include missed optimization which are not easy to
fix right away.  What I also have been trying to do is clean up the
much older ones which are more than 3-4 years old now.  This week GCC
is -2 but the week before is +17 and week before that was +3; overall
in the last year GCC is +536 (more than one a day).  For GCC, the C++
front-end is the area which has gotten out of control; not enough
developers :(.  Anyways this is getting offtopic now but it shows how
you can track things a little bit and how things can speed out of
control if an area is not covered by enough developers.

Thanks,
Andrew

>
> It's the only way we'll win.
>
> Enough practice at that and we'll start making progress.
>
> Last week was a 0 bug delta, we fixed all the reported bugs.
>
> This week I'm tackling the Venezuela locale bug and I'll see if that
> can be moved to fixed too.
>
> --
> Cheers,
> Carlos.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]