public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60126] Internal compiler error with code using pointer reshaping (gfortran 4.8.2)
Date: Sun, 09 Feb 2014 19:47:00 -0000	[thread overview]
Message-ID: <bug-60126-4-47sk1HB6Vc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60126-4@http.gcc.gnu.org/bugzilla/>

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-02-09
                 CC|                            |janus at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed with 4.7 and 4.8. It seems fixed on trunk between r201266
(2013-07-26, ICE) and r201631 (2013-08-09, OK). There are several commits in
this range without obvious suspect. The backtrace is

Program received signal SIGSEGV, Segmentation fault.
gfc_build_addr_expr (type=0x0, t=0x0) at
../../4.7_clean/gcc/fortran/trans.c:270
270      tree base_type = TREE_TYPE (t);
(gdb) bt
#0  gfc_build_addr_expr (type=0x0, t=0x0) at
../../4.7_clean/gcc/fortran/trans.c:270
#1  0x00000001000c77a3 in gfc_conv_expr_descriptor (se=0x7fff5fbff0b0,
expr=0x14250b4e0, ss=0x1421039e0)
    at ../../4.7_clean/gcc/fortran/trans-array.c:6372
#2  0x00000001000db919 in gfc_trans_pointer_assignment (expr1=0x14250aa40,
expr2=0x14250b4e0) at ../../4.7_clean/gcc/fortran/trans-expr.c:5789
#3  0x00000001000b6b42 in trans_code (code=0x14250b5a0, cond=0x0) at
../../4.7_clean/gcc/fortran/trans.c:1324
#4  0x00000001000d4cc3 in gfc_generate_function_code (ns=<optimized out>) at
../../4.7_clean/gcc/fortran/trans-decl.c:5354
#5  0x0000000100074a5d in gfc_parse_file () at
../../4.7_clean/gcc/fortran/parse.c:4460
#6  0x00000001000b27a6 in gfc_be_parse_file () at
../../4.7_clean/gcc/fortran/f95-lang.c:250
#7  0x00000001006941e0 in toplev_main (argc=2, argv=0x7fff5fbff520) at
../../4.7_clean/gcc/toplev.c:557


      reply	other threads:[~2014-02-09 19:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-09 18:56 [Bug fortran/60126] New: " mfvalin at gmail dot com
2014-02-09 19:47 ` dominiq at lps dot ens.fr [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-60126-4-47sk1HB6Vc@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).