This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: m68k bootstrapping broken
- From: Bernardo Innocenti <bernie at develer dot com>
- To: Gunther Nikl <gni at gecko dot de>
- Cc: Andreas Schwab <schwab at suse dot de>, Richard Zidlicky <rz at linux-m68k dot org>, Richard Henderson <rth at redhat dot com>, gcc at gnu dot org, gcc-patches at gcc dot gnu dot org
- Date: Tue, 13 Jan 2004 22:57:29 +0100
- Subject: Re: m68k bootstrapping broken
- Organization: Develer S.r.l.
- References: <3FFDD287.5090504@develer.com> <20040109003553.GA8001@linux-m68k.org> <3FFE1E6A.8030304@develer.com> <20040109214753.GA6321@linux-m68k.org> <400069E6.5080301@develer.com> <20040110173359.A3722@redhat.com> <4000EE16.9020907@develer.com> <20040111145603.GA5311@linux-m68k.org> <m3hdz26ycf.fsf@whitebox.m5r.de> <m3d69q6xju.fsf@whitebox.m5r.de> <20040113142341.GA59670@lorien.int.gecko.de>
Gunther Nikl wrote:
I checked again, SWAP will also produce a correct cc, here is an
updated patch.
I just built a native compiler for m68k-amigaos with a cross-compiler
that had the updated patch applied. No objects in gcc/ except m68k.o
differed. Is that a good or bad sign?
You mean "differed between your previous build and the build with
Andreas patch"?
Richard Zidlicky reported a difference in "make compare" which you
can't do unless you perform a full staged bootstrap with a native
compiler.
Flags used to build the native compiler:
CFLAGS=-O2
XCFLAGS=-m68060 -fomit-frame-pointer -fno-reorder-blocks
By the way, do you also agree that -fomit-frame-pointer is always
a win on m68k? AFAIK, gdb handles it correctly and all
-fomit-frame-pointer bugs should have been fixed.
I'll run a testsuite with -fomit-frame-pointer enabled to make
sure it doesn't break anything.
My proposal is to switch m68k to imply -fomit-frame-pointer with
-O. Of course, I think we're too late for 3.4, so it will have
to be postponed even if we all agree.
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/