public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fdarkangel at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52897] gcc 4.7.0 generates worse code than gcc 3.4.6 for m68000
Date: Sat, 13 Sep 2014 16:10:00 -0000 [thread overview]
Message-ID: <bug-52897-4-6YdqfkQRNs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52897-4@http.gcc.gnu.org/bugzilla/>
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?
There's still hope for an m68k version of LLVM though.
next prev parent reply other threads:[~2014-09-13 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 8:36 [Bug c/52897] New: " fdarkangel at gmail dot com
2012-04-07 8:37 ` [Bug c/52897] " fdarkangel at gmail dot com
2012-04-07 10:33 ` mikpe at it dot uu.se
2013-12-18 4:35 ` [Bug target/52897] " fdarkangel at gmail dot com
2014-09-12 2:34 ` fdarkangel at gmail dot com
2014-09-13 9:57 ` mikpelinux at gmail dot com
2014-09-13 16:10 ` fdarkangel at gmail dot com [this message]
2015-01-16 19:44 ` law at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-52897-4-6YdqfkQRNs@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).