public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "corsepiu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/43726] [4.5/4.6 Regression] lm32-rtems* ICE
Date: Thu, 27 May 2010 15:15:00 -0000 [thread overview]
Message-ID: <20100527151503.5840.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43726-9565@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from corsepiu at gcc dot gnu dot org 2010-05-27 15:15 -------
FWIW: I added your patch to the RTEMS lm32-gcc-4.5.0 toolchains.
With this patch applied, the ICE during building RTEMS, I had experienced does
not occur anymore. Compiling RTEMS at -O2 also seems to work.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43726
next prev parent reply other threads:[~2010-05-27 15:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 11:48 [Bug target/43726] New: " corsepiu at gcc dot gnu dot org
2010-04-12 11:52 ` [Bug target/43726] " corsepiu at gcc dot gnu dot org
2010-04-12 12:12 ` joel at gcc dot gnu dot org
2010-04-12 12:31 ` corsepiu at gcc dot gnu dot org
2010-04-12 18:47 ` [Bug target/43726] [4.5/4.6 Regression] " pinskia at gcc dot gnu dot org
2010-04-15 3:31 ` corsepiu at gcc dot gnu dot org
2010-04-15 14:07 ` rguenth at gcc dot gnu dot org
2010-05-25 23:51 ` jon at beniston dot com
2010-05-26 9:16 ` jon at beniston dot com
2010-05-27 15:06 ` jbeniston at gcc dot gnu dot org
2010-05-27 15:15 ` corsepiu at gcc dot gnu dot org [this message]
2010-05-27 15:46 ` jbeniston at gcc dot gnu dot org
2010-07-31 9:34 ` rguenth at gcc dot gnu dot org
[not found] <bug-43726-4@http.gcc.gnu.org/bugzilla/>
2010-12-16 13:20 ` rguenth at gcc dot gnu.org
2011-02-01 20:51 ` lekernel at gcc dot gnu.org
2011-02-01 20:59 ` lekernel 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=20100527151503.5840.qmail@sourceware.org \
--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).