public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55939] [4.6/4.7/4.8 regression] gcc miscompiles gmp-5.0.5 on m68k-linux
Date: Tue, 22 Jan 2013 00:23:00 -0000 [thread overview]
Message-ID: <bug-55939-4-uO0jXi5rpx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55939-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55939
--- Comment #9 from Aldy Hernandez <aldyh at redhat dot com> 2013-01-22 00:23:03 UTC ---
An image with parameters/instructions would be ideal. Heck...not ideal...great!
Thanks so much.
"mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org> wrote:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55939
--- Comment #8 from Mikael Pettersson <mikpe at it dot uu.se> 2013-01-21
23:18:34 UTC ---
I'm using the ARAnym full-system m68040 emulator -- that's the only realistic
option for testing gcc on Linux/m68k at the moment. I maintain my own small
Fedora-based distro, so if you like I can supply a disk image with that, plus
the scripts and ARAnym parameter files I use. Otherwise you can probably find
HOWTOs and pointers to images on the Debian/m68k wiki.
next prev parent reply other threads:[~2013-01-22 0:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 11:01 [Bug target/55939] New: " mikpe at it dot uu.se
2013-01-11 11:02 ` [Bug target/55939] " rguenth at gcc dot gnu.org
2013-01-11 20:06 ` mikpe at it dot uu.se
2013-01-12 16:24 ` mikpe at it dot uu.se
2013-01-16 19:49 ` law at redhat dot com
2013-01-16 20:46 ` mikpe at it dot uu.se
2013-01-17 23:20 ` mikpe at it dot uu.se
2013-01-18 4:28 ` law at redhat dot com
2013-01-21 17:20 ` aldyh at gcc dot gnu.org
2013-01-21 23:18 ` mikpe at it dot uu.se
2013-01-22 0:23 ` aldyh at redhat dot com [this message]
2013-01-29 13:24 ` aldyh at gcc dot gnu.org
2013-01-29 13:45 ` aldyh at gcc dot gnu.org
2013-01-29 17:27 ` aldyh at gcc dot gnu.org
2013-01-29 17:37 ` law at redhat dot com
2013-01-29 17:46 ` rth at gcc dot gnu.org
2013-01-29 18:03 ` mikpe at it dot uu.se
2013-01-29 18:49 ` jakub at gcc dot gnu.org
2013-01-29 19:47 ` aldyh at redhat dot com
2013-01-29 21:21 ` aldyh at gcc dot gnu.org
2013-01-30 8:54 ` mikpe at it dot uu.se
2013-01-30 8:57 ` jakub at gcc dot gnu.org
2013-01-30 21:12 ` joseph at codesourcery dot com
2013-02-18 19:39 ` aldyh at gcc dot gnu.org
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-55939-4-uO0jXi5rpx@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).