public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/48446] [4.3/4.4/4.5/4.6 Regression] internal compiler error: in gimplify_var_or_parm_decl, at gimplify.c:1946
Date: Sat, 07 May 2011 01:54:00 -0000	[thread overview]
Message-ID: <bug-48446-4-W3x9CvrFRf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48446-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48446

Jason Merrill <jason at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED
         AssignedTo|unassigned at gcc dot       |jason at gcc dot gnu.org
                   |gnu.org                     |
   Target Milestone|4.3.6                       |4.6.1

--- Comment #11 from Jason Merrill <jason at gcc dot gnu.org> 2011-05-07 01:41:03 UTC ---
Fixed for 4.6.1.


      parent reply	other threads:[~2011-05-07  1:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05  3:54 [Bug c++/48446] New: " headch at gmail dot com
2011-04-05 11:14 ` [Bug c++/48446] " rguenth at gcc dot gnu.org
2011-04-05 11:23 ` redi at gcc dot gnu.org
2011-04-05 11:30 ` [Bug c++/48446] [4.3/4.4/4.5/4.6 Regression] " redi at gcc dot gnu.org
2011-04-05 11:57 ` rguenth at gcc dot gnu.org
2011-04-07  8:31 ` jakub at gcc dot gnu.org
2011-04-07  8:36 ` jakub at gcc dot gnu.org
2011-04-07  8:55 ` jakub at gcc dot gnu.org
2011-04-10 10:47 ` rguenth at gcc dot gnu.org
2011-04-14 15:00 ` jason at gcc dot gnu.org
2011-04-14 15:22 ` jason at gcc dot gnu.org
2011-05-02 18:42 ` jason at gcc dot gnu.org
2011-05-06 22:03 ` jason at gcc dot gnu.org
2011-05-07  1:54 ` jason 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-48446-4-W3x9CvrFRf@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).