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/60450] [4.7/4.8 Regression] ICE with SHAPE intrinsic
Date: Fri, 07 Mar 2014 14:13:00 -0000	[thread overview]
Message-ID: <bug-60450-4-TAaaTbuOZD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60450-4@http.gcc.gnu.org/bugzilla/>

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

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-valid-code
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-03-07
                 CC|                            |janus at gcc dot gnu.org
            Summary|ICE with SHAPE intrinsic    |[4.7/4.8 Regression] ICE
                   |                            |with SHAPE intrinsic
     Ever confirmed|0                           |1

--- Comment #1 from janus at gcc dot gnu.org ---
The test case compiles cleanly here with 4.4 and 4.6, then I get segfaults with
4.7 and 4.8 and it works again with trunk.


With a current 4.8 branch build I get this backtrace:

f951: internal compiler error: Segmentation fault
0x8a96af crash_signal
    /home/jweil/gcc48/branch/gcc/toplev.c:332
0x547d8b gfc_clear_shape(__mpz_struct (*) [1], int)
    /home/jweil/gcc48/branch/gcc/fortran/expr.c:405
0x5b5d70 gfc_simplify_shape(gfc_expr*, gfc_expr*)
    /home/jweil/gcc48/branch/gcc/fortran/simplify.c:5540
0x5567d1 do_simplify
    /home/jweil/gcc48/branch/gcc/fortran/intrinsic.c:3810
0x563e66 gfc_intrinsic_func_interface(gfc_expr*, int)
    /home/jweil/gcc48/branch/gcc/fortran/intrinsic.c:4160
0x59fe51 resolve_unknown_f
    /home/jweil/gcc48/branch/gcc/fortran/resolve.c:2602
0x59fe51 resolve_function
    /home/jweil/gcc48/branch/gcc/fortran/resolve.c:3204
0x59fe51 gfc_resolve_expr(gfc_expr*)
    /home/jweil/gcc48/branch/gcc/fortran/resolve.c:6544
0x5a66e1 resolve_code
    /home/jweil/gcc48/branch/gcc/fortran/resolve.c:10208
0x5a8b8e resolve_codes
    /home/jweil/gcc48/branch/gcc/fortran/resolve.c:15061
0x599562 gfc_resolve
    /home/jweil/gcc48/branch/gcc/fortran/resolve.c:15089
0x58dda2 resolve_all_program_units
    /home/jweil/gcc48/branch/gcc/fortran/parse.c:4406
0x58dda2 gfc_parse_file()
    /home/jweil/gcc48/branch/gcc/fortran/parse.c:4673
0x5c9de5 gfc_be_parse_file
    /home/jweil/gcc48/branch/gcc/fortran/f95-lang.c:189


  reply	other threads:[~2014-03-07 14:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 21:24 [Bug fortran/60450] New: " dave.allured at noaa dot gov
2014-03-07 14:13 ` janus at gcc dot gnu.org [this message]
2014-03-07 14:36 ` [Bug fortran/60450] [4.7/4.8 Regression] " janus at gcc dot gnu.org
2014-03-07 14:42 ` janus at gcc dot gnu.org
2014-03-07 18:24 ` janus at gcc dot gnu.org
2014-03-07 22:25 ` dave.allured at noaa dot gov
2014-03-08 13:59 ` janus at gcc dot gnu.org
2014-03-08 14:05 ` janus at gcc dot gnu.org
2014-03-09 18:25 ` dave.allured at noaa dot gov
2014-03-09 18:45 ` janus at gcc dot gnu.org
2014-03-09 19:01 ` janus at gcc dot gnu.org
2014-03-09 19:06 ` janus at gcc dot gnu.org
2014-03-09 19:40 ` dave.allured at noaa dot gov

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-60450-4-TAaaTbuOZD@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).