public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52375] [4.6 Regression] internal compiler error: in extract_insn, at recog.c:2123 at -O3 -mfpu=neon
Date: Fri, 12 Apr 2013 16:18:00 -0000 [thread overview]
Message-ID: <bug-52375-4-K6wy00mStP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52375-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52375
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
Target Milestone|4.6.4 |4.7.0
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-04-12 16:18:06 UTC ---
The 4.6 branch has been closed, fixed in GCC 4.7.0.
prev parent reply other threads:[~2013-04-12 16:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 19:42 [Bug middle-end/52375] New: [4.7 " Bernhard.Rosenkranzer at linaro dot org
2012-02-24 20:04 ` [Bug middle-end/52375] " mikpe at it dot uu.se
2012-02-24 20:38 ` Bernhard.Rosenkranzer at linaro dot org
2012-02-24 23:04 ` Bernhard.Rosenkranzer at linaro dot org
2012-02-24 23:22 ` steven at gcc dot gnu.org
2012-02-25 12:10 ` mikpe at it dot uu.se
2012-02-25 12:57 ` steven at gcc dot gnu.org
2012-02-25 14:47 ` Bernhard.Rosenkranzer at linaro dot org
2012-02-25 19:18 ` mikpe at it dot uu.se
2012-02-27 9:19 ` rguenth at gcc dot gnu.org
2012-02-27 9:21 ` rguenth at gcc dot gnu.org
2012-02-27 10:42 ` [Bug middle-end/52375] [4.6/4.7 " rguenth at gcc dot gnu.org
2012-02-27 11:17 ` jakub at gcc dot gnu.org
2012-02-27 12:57 ` [Bug target/52375] " jakub at gcc dot gnu.org
2012-02-27 15:55 ` jakub at gcc dot gnu.org
2012-02-27 16:18 ` [Bug target/52375] [4.6 " jakub at gcc dot gnu.org
2013-04-12 16:18 ` jakub at gcc dot gnu.org [this message]
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-52375-4-K6wy00mStP@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).