GCC 3.0.4
Mark Mitchell
mark@codesourcery.com
Sun Feb 3 22:43:00 GMT 2002
Please consider the GCC 3.0 branch slushed at this time. All
code patches will now require my approval, as we are now preparing
for the 3.0.4 release on February 15th.
Unfortunately, I'll be travelling through the 12th. I'll be
reading email, but sporadically. My inability to respond may or may
not require a brief postponement of the GCC 3.0.4 release.
Below, here are the unresolved issues that have been brought to
my attention as important bugs to fix for this release. If you
have additional issues, or additional information about these
issues, please let me know as soon as possible.
Yours,
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
"Richard B. Kreckel" <kreckel@ginac.de>
Rainer Orth's patch on Mon Jul 16 2001 broke CLN on Tru64.
I requested filing of a PR.
Bob Wilson <bwilson@tensilica.com>
Would like Xtensa port in GCC 3.0.4.
Don Lindsay <lindsayd@cisco.com>
PR5198
PR5143
There are build failures in cross compilers to AMR and m68k.
"Bradley D. LaRonde" <brad@ltc.com>
PR5405 -- 3.0.3 "introduced the -mtune brokenness"
Phil Blundell <pb@nexus.co.uk>
PR5209 -- Bootstrap problem. Regression from 3.0.2.
Richard Henderson <rth@redhat.com>
http://gcc.gnu.org/ml/gcc-patches/2002-01/msg00194.html
This is a problem with loop unrolling that comes from
expand_end_loop incorrectly rotating the loop. It affects
loop-10.c and is a regression from GCC 2.95.
Zack Weinberg <zack@codesourcery.com>
3.0.3 mishandles #line in the middle of a function, emitting
incorrect debugging output.
Neil fixed this problem on the mainline. I asked Zack to apply
Neil's patch to the branch, if this is a regression from GCC 2.95.
More information about the Gcc
mailing list