public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51966] [4.6/4.7 Regression] ICE in gfc_conv_array_constructor_expr
Date: Wed, 25 Jan 2012 08:53:00 -0000	[thread overview]
Message-ID: <bug-51966-4-opl0LbxRnj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51966-4@http.gcc.gnu.org/bugzilla/>

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

--- Comment #8 from Tobias Burnus <burnus at gcc dot gnu.org> 2012-01-25 08:26:16 UTC ---
FIXED on the trunk (for 4.7) and on the 4.6 branch.

Thanks for the report!

If the issue blocks you, you could consider downgrading to 4.5. Alternatively,
you could build GCC yourself or download a newer [than today] 4.6 or pre-4.7.0
build. (Cf. http://gcc.gnu.org/wiki/GFortranBinaries and
http://gcc.gnu.org/wiki/GFortranDistros )


      parent reply	other threads:[~2012-01-25  8:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-23 14:08 [Bug fortran/51966] New: internal compiler error peter.tromso at gmail dot com
2012-01-23 15:02 ` [Bug fortran/51966] " peter.tromso at gmail dot com
2012-01-23 15:19 ` [Bug fortran/51966] [4.6/4.7 Regression] ICE in gfc_conv_array_constructor_expr burnus at gcc dot gnu.org
2012-01-23 15:21 ` dominiq at lps dot ens.fr
2012-01-23 16:53 ` jakub at gcc dot gnu.org
2012-01-24 10:13 ` burnus at gcc dot gnu.org
2012-01-24 10:20 ` burnus at gcc dot gnu.org
2012-01-25  8:39 ` burnus at gcc dot gnu.org
2012-01-25  8:50 ` burnus at gcc dot gnu.org
2012-01-25  8:53 ` burnus 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-51966-4-opl0LbxRnj@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).