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 c/52773] internal error: in replace_pseudos_in, at reload1.c:577
Date: Thu, 29 Mar 2012 18:16:00 -0000 [thread overview]
Message-ID: <bug-52773-4-8emMOCGNAA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52773-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52773
Mikael Pettersson <mikpe at it dot uu.se> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mikpe at it dot uu.se
--- Comment #1 from Mikael Pettersson <mikpe at it dot uu.se> 2012-03-29 18:11:33 UTC ---
I can reproduce the ICE with gcc 4.8-20120325, 4.7-20120324, and 4.6-20120323,
but not with gcc-4.5-20120322 or 4.4.7, all built as crosses to m68k-linux.
next prev parent reply other threads:[~2012-03-29 18:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 14:58 [Bug c/52773] New: " fdarkangel at gmail dot com
2012-03-29 18:16 ` mikpe at it dot uu.se [this message]
2012-03-29 22:17 ` [Bug c/52773] " mikpe at it dot uu.se
2013-04-08 15:52 ` alanh at fairlite dot co.uk
2013-04-08 17:11 ` mikpe at it dot uu.se
2013-06-17 17:35 ` alanh at fairlite dot co.uk
2013-06-18 9:03 ` mikpe at it dot uu.se
2013-06-21 11:07 ` mikpe at it dot uu.se
2013-12-18 4:37 ` fdarkangel at gmail dot com
2013-12-18 8:44 ` mikpelinux at gmail dot com
2014-09-12 2:26 ` [Bug rtl-optimization/52773] " fdarkangel at gmail dot com
2014-09-13 9:48 ` mikpelinux at gmail dot com
2015-01-17 7:36 ` law at gcc dot gnu.org
2015-01-17 7:42 ` law at redhat dot com
2022-01-10 10:12 ` pinskia at gcc dot gnu.org
2022-01-10 10:12 ` pinskia 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-52773-4-8emMOCGNAA@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).