public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/37448] gcc 4.3.1 cannot compile big function
Date: Tue, 18 Jan 2011 14:49:00 -0000 [thread overview]
Message-ID: <bug-37448-4-gBiq5tRUoI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-37448-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37448
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |47344
Target Milestone|4.3.6 |---
Summary|[4.3/4.4/4.5/4.6 |gcc 4.3.1 cannot compile
|Regression] gcc 4.3.1 |big function
|cannot compile big function |
Known to fail| |4.6.0
--- Comment #42 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-01-18 14:28:00 UTC ---
PR47344 now tracks the regression property of this bug.
next parent reply other threads:[~2011-01-18 14:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-37448-4@http.gcc.gnu.org/bugzilla/>
2011-01-18 14:49 ` rguenth at gcc dot gnu.org [this message]
2011-01-18 15:11 ` hubicka at gcc dot gnu.org
2011-01-18 15:15 ` hubicka at gcc dot gnu.org
2012-10-25 23:52 ` steven at gcc dot gnu.org
2012-10-26 2:05 ` lucier at math dot purdue.edu
2012-10-26 15:23 ` hubicka at gcc dot gnu.org
2012-10-26 16:48 ` hubicka at gcc dot gnu.org
2012-10-26 17:29 ` steven at gcc dot gnu.org
2013-03-06 10:43 ` [Bug middle-end/37448] [4.6/4.7/4.8 Regression] " steven at gcc dot gnu.org
2013-03-06 10:46 ` [Bug middle-end/37448] " rguenth at gcc dot gnu.org
2008-09-09 18:35 [Bug c/37448] New: gcc 4.3.1 " grue at diku dot dk
2008-09-10 8:02 ` [Bug middle-end/37448] " grue at diku dot dk
2008-09-10 8:03 ` grue at diku dot dk
2008-09-10 8:04 ` rguenth at gcc dot gnu 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-37448-4-gBiq5tRUoI@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).