This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/53386] Bad assembly code produced for m68000
- From: "ljalvs at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 18 May 2012 17:00:11 +0000
- Subject: [Bug target/53386] Bad assembly code produced for m68000
- Auto-submitted: auto-generated
- References: <bug-53386-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386
--- Comment #13 from Luis Alves <ljalvs at gmail dot com> 2012-05-18 17:00:11 UTC ---
I've built gcc with the m68k/linux.h patched for the 68000 but it's not working
as expected.
As test I've used linux kernel 3.3
Results are compared to the use of gcc-4.2.4 vs gcc-4.6.3 (gcc-4.7.0 doesn't
even build itself because of an ICE).
(Using the same kernel configuration, only changed gcc version)
Kernel Size:
4.2.4: 2158592 bytes
4.6.3: 2244608 bytes (around 4% increase)
Using 4.2.4 kernel boots as expected and everything works fine.
With 4.6.3 the kernel boots and after a few seconds starts a non-stop SPAM of
BUGs:
[...]
BUG: scheduling while atomic: ksoftirqd/0/3/0x00000000
[...]
BUG: scheduling while atomic: kthreadd/2/0x00000000
[...]
BUG: scheduling while atomic: kworker/0:0/4/0x04000002
[...]
Until eventually panics.
Anyway, building gcc for target "m68k-uclinuxoldabi" is a bit awkward.
I've tried to build and the message I got is that target will be removed soon.
Also it would give a lot of work to integrate it with the existing tools
because of the resulting prefix (binutils, elf2flt, ...).
As of "gcc -m68000" not generating correct code for the 68000 I would still say
that IT IS a gcc bug...