From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7383 invoked by alias); 9 Dec 2010 17:04:55 -0000 Received: (qmail 7357 invoked by uid 22791); 9 Dec 2010 17:04:54 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 09 Dec 2010 17:04:50 +0000 From: "tstdenis at elliptictech dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/18501] [4.3/4.4/4.5/4.6 Regression] Missing 'used uninitialized' warning (CCP) X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Keywords: diagnostic X-Bugzilla-Severity: minor X-Bugzilla-Who: tstdenis at elliptictech dot com X-Bugzilla-Status: REOPENED X-Bugzilla-Priority: P5 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.3.6 X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Thu, 09 Dec 2010 17:04:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-12/txt/msg01011.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18501 --- Comment #46 from Tom St Denis 2010-12-09 17:03:37 UTC --- (In reply to comment #44) > (In reply to comment #43) > > Maybe it's high time someone address this shortcoming as opposed to adding > > additional language front ends. If you can't even get the core ones right... > > Generally the people who add front-ends aren't the people working on the > middle-end and optimisers, so work on one doesn't take resources away from the > other. It still adds work to the project as a whole and serves as a distraction for new people who have the time to contribute. > Feel free to pay someone to fix it if this is important to you. Just sayin' If fixing known bugs is not a priority then of what value is this project other than being free? I thought the whole point was to also be correct. Granted this isn't a show-stopper as far as bugs go, but the laissez-faire "if you hate it fix it yourself" trend in OSS is really annoying. When I ran my own OSS projects I never told the users "nyah nyah fix it yourself!" When I ran out of time to work on the OSS projects I gave them up, but so long as I called myself a maintainer I addressed issues as best as I could. I'd almost rather they leave it as WONTFIX then just leaving it open. I'd also be happier if they documented this class of SSA fail in the man page so people don't walk into it [as I and others have].