public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu.se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/52383] [4.6 Regression] miscompiles Perl on m68k
Date: Tue, 22 May 2012 10:06:00 -0000 [thread overview]
Message-ID: <bug-52383-4-8lBJAcE0NO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52383-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52383
Mikael Pettersson <mikpe at it dot uu.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpe at it dot uu.se
--- Comment #5 from Mikael Pettersson <mikpe at it dot uu.se> 2012-05-22 08:35:14 UTC ---
(In reply to comment #4)
> Upgrading didn’t help, but in the meantime, I got it built.
> I blame ARAnyM, as it succeeds on a box I put Petr’s .deb on…
> so no wonder Andreas couldn’t reproduce it.
FWIW, I've just built perl-5.12.4 with gcc-4.6.3 (+ patches) on ARAnyM (0.9.11)
running a Linux 3.x kernel. It seems to work fine, and the make_patchnum.pl
error you mentioned did not occur. IOW, I'm more inclined to suspect Debian's
gcc-4.6 (at the time) than ARAnyM.
next prev parent reply other threads:[~2012-05-22 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-25 22:54 [Bug regression/52383] New: gcc-4.6 regression: " tg at mirbsd dot org
2012-02-25 23:52 ` [Bug regression/52383] " tg at mirbsd dot org
2012-02-27 9:28 ` [Bug regression/52383] [4.6 Regression] " rguenth at gcc dot gnu.org
2012-03-02 17:13 ` schwab@linux-m68k.org
2012-03-03 15:50 ` tg at mirbsd dot org
2012-04-22 15:42 ` tg at mirbsd dot org
2012-05-22 10:06 ` mikpe at it dot uu.se [this message]
2012-05-22 12:39 ` tg at mirbsd dot 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-52383-4-8lBJAcE0NO@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).