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/50163] Internal compiler error: initialization expression
Date: Tue, 23 Aug 2011 10:21:00 -0000	[thread overview]
Message-ID: <bug-50163-4-7b5FtUsIqo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50163-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2011-08-23
     Ever Confirmed|0                           |1

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2011-08-23 10:07:42 UTC ---
Confirmed on 4.4.6, 4.5.3, 4.6.1, and trunk. g95 and ifort reject the code with

[macbook] f90/bug% g95 pr50163.f90
In file pr50163.f90:3

integer :: iloc=index(xx,'bb')
                      1
Error: Variable 'xx' at (1) cannot appear in an initialization expression
[macbook] f90/bug% ifc pr50163.f90
pr50163.f90(3): error #6592: This symbol must be a defined parameter, an
enumerator, or an argument of an inquiry function that evaluates to a
compile-time constant.   [XX]
integer :: iloc=index(xx,'bb')
----------------------^
pr50163.f90(3): error #6973: This is not a valid initialization expression.  
[INDEX]
integer :: iloc=index(xx,'bb')
----------------^
compilation aborted for pr50163.f90 (code 1)

The segmentation fault is due to

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000
check_init_expr (e=0x141f1c640) at ../../work/gcc/fortran/expr.c:1969
1969          if (a->expr->expr_type != EXPR_ARRAY)
(gdb) bt
#0  check_init_expr (e=0x141f1c640) at ../../work/gcc/fortran/expr.c:1969
#1  0x000000010002e778 in gfc_reduce_init_expr (expr=0x3) at
../../work/gcc/fortran/expr.c:2626
Current language:  auto; currently c++
(gdb) p *a
$3 = {
  name = 0x0, 
  label = 0x0, 
  missing_arg_type = BT_LOGICAL, 
  expr = 0x0, 
  next = 0x141f1cac0
}


  reply	other threads:[~2011-08-23 10:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23  9:41 [Bug fortran/50163] New: " pmason at ricardo dot com
2011-08-23 10:21 ` dominiq at lps dot ens.fr [this message]
2011-08-23 12:14 ` [Bug fortran/50163] [4.3/4.4/4.5/4.6/4.7 Regression] ICE: " burnus at gcc dot gnu.org
2011-08-24 13:26 ` burnus at gcc dot gnu.org
2011-08-24 14:02 ` jakub at gcc dot gnu.org
2011-08-25  8:33 ` burnus at gcc dot gnu.org
2011-08-30  7:26 ` [Bug fortran/50163] [4.4/4.5 " burnus at gcc dot gnu.org
2011-08-30 12:24 ` [Bug fortran/50163] [4.4/4.5/4.6/4.7 " burnus at gcc dot gnu.org

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-50163-4-7b5FtUsIqo@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).