This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 3.3 release
On Mon, Mar 24, 2003 at 12:07:57PM +0100, Andreas Schwab wrote:
> Gunther Nikl <gni at gecko dot de> writes:
>
> |> On Fri, Mar 21, 2003 at 20:56:41 -0500, Nathanael Nerode wrote:
> |> > It would also be nice if 3.3 could bootstrap itself successfully on
> |> > m68k; there seem to be a number of frightening bugs preventing 3.2 from
> |> > doing so, but the m68k experts will have to look at them.
> |>
> |> AFAICT, the bug(s) preventing a bootstrap on m68k is (are) with
> |> "long long". After I disabled "long long" in auto-host.h I could
> |> build a working 3.2.2 on m68k with GCC 2.95.2 and 2.7.2.1. I suspect
> |> thats is a long standing problem still present since a m68k GCC 3.2.2
> |> with "long long" enabled in auto-host.h shows the same symtoms as a
> |> natively built GCC 3.2.2 (compiled with either 2.95.2 or 2.7.2.1).
>
> Have you already tried with current CVS where the iordi3 bug is fixed?
I checked 3.2.2 with the iordi3 patch included and a native GCC 3.2.2 is
still broken :-/ I verified that the patch is included in the used 3.2.2
cc1 by compiling the sample testcase from the pr. (BTW, 2.7.2.1 doesn't
have that problem since the generated code for the pr testcase is correct.
egcs 1.0.3 and 1.1 do have that bug).
However, I also tried a native 3.3/20030303 and that version _does_ work.
At least it could compile 3.2.2 with "long long" enabled and the resulting
xgcc didn't barf when compiling libgcc.a as it did when compiled by eg.
2.95.2 and "long long" enabled. I didn't try a bootstrap since that would
need to much time which I currently don't have.
Building a native m68k 3.3/20030303 with a m68k cross-gcc showed a problem
during compilation of ra-colorize.c with -O1. With -O1 the compiler emits
unused and incomplete switch jump-tables eg. in ra-colorize.c/reset_lists.
I guess this happens when inlining put_web(). Specifying -fgcse fixes that.
Gunther