This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug rtl-optimization/15296] [3.4 only] Delayed branch scheduling causing invalid code on cris-*
- From: "bangerth at dealii dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 May 2004 18:21:11 -0000
- Subject: [Bug rtl-optimization/15296] [3.4 only] Delayed branch scheduling causing invalid code on cris-*
- References: <20040505140818.15296.hp@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From bangerth at dealii dot org 2004-05-26 18:21 -------
All of us bugzilla people quite frequently use the known-to-{work,fail}
fields to fill which _branches_ work. For example, if something is
known to fail with the 3.4.0 release but to be fixed on mainline, then
3.5.0 will be listed in the known-to-work field. This actually makes some
sense, since if it is fixed on the mainline, then there needs to be a
testcase in the testsuite which (at least ideally) should prevent this
problem from re-appearing on mainline, thus guaranteeing that the actual
3.5.0 release will also work.
This procedure may not be documented, but us bugzilla guys all seem to use
it.
W.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15296