[Bug target/53386] Bad assembly code produced for m68000

2020-02-20 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 Jeffrey A. Law changed: What|Removed |Added Status|SUSPENDED |RESOLVED Resolution|---

[Bug target/53386] Bad assembly code produced for m68000

2015-01-19 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 Jeffrey A. Law changed: What|Removed |Added Status|UNCONFIRMED |SUSPENDED Last reconfirmed|

[Bug target/53386] Bad assembly code produced for m68000

2012-05-18 Thread ljalvs at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 --- Comment #13 from Luis Alves 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.

[Bug target/53386] Bad assembly code produced for m68000

2012-05-17 Thread ljalvs at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 --- Comment #12 from Luis Alves 2012-05-17 15:44:12 UTC --- (In reply to comment #10) > See the gcc-patches thread I referred to in #c8, gcc-4.3 also changed > low-level > ABI details, with the consequence that gcc-4.2 and gcc-4.3 generate > inc

[Bug target/53386] Bad assembly code produced for m68000

2012-05-17 Thread sch...@linux-m68k.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 Andreas Schwab changed: What|Removed |Added Severity|blocker |normal --- Comment #11 from Andreas Schw

[Bug target/53386] Bad assembly code produced for m68000

2012-05-17 Thread mikpe at it dot uu.se
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 --- Comment #10 from Mikael Pettersson 2012-05-17 15:02:51 UTC --- See the gcc-patches thread I referred to in #c8, gcc-4.3 also changed low-level ABI details, with the consequence that gcc-4.2 and gcc-4.3 generate incompatible code for m68k-ucli

[Bug target/53386] Bad assembly code produced for m68000

2012-05-17 Thread ljalvs at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 --- Comment #9 from Luis Alves 2012-05-17 14:29:07 UTC --- Thanks Mikael, But... will I have any (future) problems if I just change the flags in the ? In a small test I've made that solutions seems to produce good code for the 68000 but I'm af

[Bug target/53386] Bad assembly code produced for m68000

2012-05-17 Thread mikpe at it dot uu.se
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 --- Comment #8 from Mikael Pettersson 2012-05-17 12:57:20 UTC --- Fallout from a deliberate ABI change in 4.3.x, see and its followups. I don't like the way an existing target triplet was

[Bug target/53386] Bad assembly code produced for m68000

2012-05-17 Thread mikpe at it dot uu.se
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 --- Comment #7 from Mikael Pettersson 2012-05-17 11:31:35 UTC --- gcc-4.3.x changed gcc/config.gcc: --- gcc-4.2.4/gcc/config.gcc2008-03-13 20:11:43.0 +0100 +++ gcc-4.3.6/gcc/config.gcc2011-02-25 00:02:14.0 +0100 ... -m68k

[Bug target/53386] Bad assembly code produced for m68000

2012-05-17 Thread mikpe at it dot uu.se
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 --- Comment #6 from Mikael Pettersson 2012-05-17 11:09:08 UTC --- The behaviour changed between gcc-4.2.4 (ok) and gcc-4.3.6 (bad).

[Bug target/53386] Bad assembly code produced for m68000

2012-05-17 Thread ljalvs at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 Luis Alves changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

[Bug target/53386] Bad assembly code produced for m68000

2012-05-17 Thread mikpe at it dot uu.se
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 Mikael Pettersson changed: What|Removed |Added CC||mikpe at it dot uu.se --- Comment #4

[Bug target/53386] Bad assembly code produced for m68000

2012-05-17 Thread ljalvs at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 --- Comment #3 from Luis Alves 2012-05-17 10:19:11 UTC --- Thanks a lot Andreas, Changed those flags to true and it's working good now. Also a minor correction: I was trying to build gcc 4.6.3 (not 4.6.4). (I've changed status to RESOLVED-INVA

[Bug target/53386] Bad assembly code produced for m68000

2012-05-17 Thread ljalvs at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 Luis Alves changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version|4.6.4

[Bug target/53386] Bad assembly code produced for m68000

2012-05-17 Thread sch...@linux-m68k.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53386 --- Comment #1 from Andreas Schwab 2012-05-17 08:23:45 UTC --- config/m68k/linux.h: /* for 68k machines this only needs to be TRUE for the 68000 */ #undef STRICT_ALIGNMENT #define STRICT_ALIGNMENT 0 #undef M68K_HONOR_TARGET_STRICT_ALIGNMENT #def