This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC 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]

[Bug tree-optimization/18501] [4.3/4.4/4.5/4.6 Regression] Missing 'used uninitialized' warning (CCP)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18501

--- Comment #46 from Tom St Denis <tstdenis at elliptictech dot com> 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].


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