[Bug target/52897] gcc 4.7.0 generates worse code than gcc 3.4.6 for m68000

2015-01-16 Thread law at redhat dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52897 Jeffrey A. Law law at redhat dot com changed: What|Removed |Added Priority|P3 |P5

[Bug target/52897] gcc 4.7.0 generates worse code than gcc 3.4.6 for m68000

2014-09-13 Thread mikpelinux at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52897 --- Comment #5 from Mikael Pettersson mikpelinux at gmail dot com --- I'm afraid that improving performance on m68k is not a high priority for most gcc developers. Interested parties may have to do the work themselves, or hire someone to do it

[Bug target/52897] gcc 4.7.0 generates worse code than gcc 3.4.6 for m68000

2014-09-13 Thread fdarkangel at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52897 --- Comment #6 from fdarkangel at gmail dot com --- I don't think hobbyist Sega Genesis devs are willing to hire gcc a hacker to solve the issue. My bet is no one in the world with money is using m68k. Why not drop m68k altogether then?

[Bug target/52897] gcc 4.7.0 generates worse code than gcc 3.4.6 for m68000

2014-09-11 Thread fdarkangel at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52897 --- Comment #4 from fdarkangel at gmail dot com --- Bump. Any news? gcc 4.9.1 doesn't look good either.

[Bug target/52897] gcc 4.7.0 generates worse code than gcc 3.4.6 for m68000

2013-12-17 Thread fdarkangel at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52897 --- Comment #3 from fdarkangel at gmail dot com --- Persists in gcc 4.8.2.