From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 119719 invoked by alias); 30 Oct 2016 04:41:23 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 119674 invoked by uid 89); 30 Oct 2016 04:41:17 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:1536 X-HELO: mail-yb0-f173.google.com X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ATPaENK2B+pJc12FRvaX/ulUyLISrEOs34a/fRaDW84=; b=GAdpq9O1lk+GYkfZrTKLMgIOiFjpXujzFgJ8eNskSYHA4kxAfWiuDMZx60AiOT8qTX AxZX2GFdnGROT5YBGPmESdO86NXKW2cITYR0yWhNzfMZjdBZ1cXtumLmIH4hPqxJoiIo LEao+auCTFufrj99ljs6f4QJ+293y6ftfVOrFv3sM0F5vd15qaR0sovrHG54FVgP+Oqx x8OvL/FmPP7QB9TM/3av6C3tnNukO6jpL/tMlXnY86+9yYdVKwW3uSV+LElDs21geSlN LR7PoxgooPq7d9RI0puGNLqsTlwUZM8j4ScEx4iErD8t3F3g91Ty4u3tyZYENvXGBwYb 93sA== X-Gm-Message-State: ABUngvd6ccX4ShFEnPAlFc2D/W4+35NoQ/+CN/9RTwtDpwQ8r3zbW029efuPf5N5/Al28mDEd6YIGWimSOxrXQ== X-Received: by 10.37.200.193 with SMTP id y184mr17616055ybf.164.1477802465690; Sat, 29 Oct 2016 21:41:05 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <520f3153-9ae0-f6da-6831-fb371d31ed90@redhat.com> References: <520f3153-9ae0-f6da-6831-fb371d31ed90@redhat.com> From: Andrew Pinski Date: Sun, 30 Oct 2016 04:41:00 -0000 Message-ID: Subject: Re: GLIBC bug list on sourceware.org To: "Carlos O'Donell" Cc: Adhemerval Zanella , GNU C Library Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2016-10/txt/msg00593.txt.bz2 On Sat, Oct 29, 2016 at 9:01 PM, Carlos O'Donell 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.