From: Andrew Pinski <pinskia@gmail.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: GLIBC bug list on sourceware.org
Date: Sun, 30 Oct 2016 04:41:00 -0000 [thread overview]
Message-ID: <CA+=Sn1nXica9Q8htKdyyZ1=rThhcdELidC8DtZOY1eYgqM9=Ag@mail.gmail.com> (raw)
In-Reply-To: <520f3153-9ae0-f6da-6831-fb371d31ed90@redhat.com>
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.
next prev parent reply other threads:[~2016-10-30 4:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 19:36 Adhemerval Zanella
2016-10-24 19:48 ` Chris Leonard
2016-10-25 2:27 ` Siddhesh Poyarekar
2016-10-25 3:33 ` Carlos O'Donell
2016-10-30 4:01 ` Carlos O'Donell
2016-10-30 4:41 ` Andrew Pinski [this message]
2016-10-31 9:31 ` Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+=Sn1nXica9Q8htKdyyZ1=rThhcdELidC8DtZOY1eYgqM9=Ag@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).