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/51520] [4.6 Regression] ICE in gfortran 4.6.x
Date: Fri, 15 Feb 2013 07:46:00 -0000	[thread overview]
Message-ID: <bug-51520-4-LZCutLu6Iz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51520-4@http.gcc.gnu.org/bugzilla/>


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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |burnus at gcc dot gnu.org
         Resolution|                            |WONTFIX

--- Comment #8 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-02-15 07:45:58 UTC ---
I close this now as WONTFIX.

Given that it works in the current release 4.7.x and in the
very-soon-to-be-released 4.8, it is simply very unlikely that anyone will work
on this PR.

Thanks for reporting the bug – and sorry for both the breakage and for not
fixing it. I hope that using GCC 4.7/4.8 is an alternative.


      parent reply	other threads:[~2013-02-15  7:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12 22:54 [Bug fortran/51520] New: ICE in gfortran 4.6.2, x86_64 adrian at llnl dot gov
2011-12-12 23:21 ` [Bug fortran/51520] [4.6 Regression] " dominiq at lps dot ens.fr
2011-12-13  8:49 ` burnus at gcc dot gnu.org
2011-12-13  9:19 ` burnus at gcc dot gnu.org
2011-12-13 12:55 ` dominiq at lps dot ens.fr
2012-01-12 10:08 ` burnus at gcc dot gnu.org
2012-03-01 15:29 ` jakub at gcc dot gnu.org
2012-11-24 13:14 ` [Bug fortran/51520] [4.6 Regression] ICE in gfortran 4.6.x janus at gcc dot gnu.org
2012-11-24 14:13 ` janus at gcc dot gnu.org
2013-02-15  7:46 ` 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-51520-4-LZCutLu6Iz@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).