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?
Not yet. I already fetched that patch, applied it to my 3.3 snapshot and
compiled cc1. Then I checked the result of the testcase from the pr.
cc1 without patch trashed "d2", cc1 with that patch didn't. I am going
to check 3.2.2 and a 3.3 snapshot with that patch on my m68k system.
It will take some time since I need one hour to build an unoptimized 3.x
compiler with GCC 2.x. I guess using a 3.x version will increase compile
time.
Gunther