public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/55174] [4.6 Regression] Segmentation fault with bad array reference
Date: Fri, 02 Nov 2012 10:55:00 -0000	[thread overview]
Message-ID: <bug-55174-4-dQkOmCv9VF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55174-4@http.gcc.gnu.org/bugzilla/>


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

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-invalid-code
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-11-02
                 CC|                            |janus at gcc dot gnu.org
            Summary|internal compiler error:    |[4.6 Regression]
                   |Segmentation fault with bad |Segmentation fault with bad
                   |array reference             |array reference
     Ever Confirmed|0                           |1

--- Comment #2 from janus at gcc dot gnu.org 2012-11-02 10:54:50 UTC ---
(In reply to comment #1)
> It looks like it has been fixed on trunk (aka 4.8.0).

For me it also works with:

gcc version 4.7.2 20120920 [gcc-4_7-branch revision 191568] (SUSE Linux)

(while it fails with 4.7.0 and 4.6.0).

Note: The 4.6 branch is still maintained, so we should consider fixing it
there.


  parent reply	other threads:[~2012-11-02 10:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-02  0:44 [Bug fortran/55174] New: internal compiler error: " john.harper at vuw dot ac.nz
2012-11-02  2:57 ` [Bug fortran/55174] " kargl at gcc dot gnu.org
2012-11-02 10:55 ` janus at gcc dot gnu.org [this message]
2012-11-04 20:41 ` [Bug fortran/55174] [4.6 Regression] " harper at msor dot vuw.ac.nz
2012-11-04 22:23 ` janus at gcc dot gnu.org
2012-11-05  0:03 ` harper at msor dot vuw.ac.nz
2012-11-05  0:52 ` harper at msor dot vuw.ac.nz

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-55174-4-dQkOmCv9VF@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).