This is the mail archive of the
mailing list for the GCC project.
Re: PATCH: tree-ssa-sink breaks stack layout
- From: Eric Botcazou <ebotcazou at adacore dot com>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: gcc-patches at gcc dot gnu dot org, Ian Lance Taylor <iant at google dot com>, Richard Guenther <richard dot guenther at gmail dot com>, Sandra Loosemore <sandra at codesourcery dot com>, Daniel Berlin <dberlin at dberlin dot org>
- Date: Mon, 6 Apr 2009 19:13:14 +0200
- Subject: Re: PATCH: tree-ssa-sink breaks stack layout
- References: <49D25676.firstname.lastname@example.org> <email@example.com> <49D90534.firstname.lastname@example.org>
> If I understand correctly, you're arguing that delivering broken
> software to users is better than papering over a bug because the
> brokenness will motivate people to fix the underlying problem, resulting
> in a better long-term outcome.
It depends on what you call "broken software". Would GCC stop being "broken
software" if we paper over this particular bug? What about papering over the
hundreds of other bugs we know GCC contains? We would need some criterion.
> The reason that we've not fixed this problem is because it's hard. Is
> anybody committed to fixing this for 4.5? If not, there's no guarantee
> that it will be fixed in that timeframe. Isn't it better to reduce the
> impact of the bug, in case it's not in fact fixed?
This bug has been known for years and seems to occur extremely rarely in
pratice, so why rushing to paper over it now? Just because it's Sandra and
we know that GCC guys are extremely gallant? :-)