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/56852] [4.6/4.7/4.8/4.9 Regression] ICE on invalid: "Bad array reference" for an undeclared loop variable
Date: Sat, 06 Apr 2013 09:33:00 -0000	[thread overview]
Message-ID: <bug-56852-4-wHdvucmgNv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56852-4@http.gcc.gnu.org/bugzilla/>


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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-04-06
            Summary|ICE on invalid: "Bad array  |[4.6/4.7/4.8/4.9
                   |reference" for an           |Regression] ICE on invalid:
                   |undeclared loop variable    |"Bad array reference" for
                   |                            |an undeclared loop variable
     Ever Confirmed|0                           |1

--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2013-04-06 09:33:10 UTC ---
Confirmed. Revision 164285 (2010-09-14) gives the error

pr56852.f90:5.14:

  read(0) (a(i),i=1,4)
              1
Error: Symbol 'i' at (1) has no IMPLICIT type

without ICE. Revision 164728 (2010-09-29) gives the same error plus the ICE

program test
            1
Internal Error at (1):
gfc_variable_attr(): Bad array reference

Backtrace for revision 197238

#0  gfc_variable_attr (expr=0x141a141d0, ts=0x0) at
../../_clean/gcc/fortran/primary.c:2135
#1  0x00000001000863b0 in gfc_expr_attr (e=<value optimized out>) at
../../_clean/gcc/fortran/primary.c:2267
#2  0x000000010003c5f9 in gfc_check_vardef_context (e=0x141a141d0,
pointer=false, alloc_obj=<value optimized out>, own_scope=<value optimized
out>, 
    context=0x100b3949f "item in READ") at ../../_clean/gcc/fortran/expr.c:4706
#3  0x000000010009cc2d in resolve_code (code=<value optimized out>, ns=<value
optimized out>) at ../../_clean/gcc/fortran/resolve.c:8150
#4  0x000000010009a90c in gfc_resolve_blocks (b=<value optimized out>,
ns=<value optimized out>) at ../../_clean/gcc/fortran/resolve.c:8885
#5  0x000000010009adc2 in resolve_code (code=<value optimized out>, ns=<value
optimized out>) at ../../_clean/gcc/fortran/resolve.c:9557
#6  0x000000010009a90c in gfc_resolve_blocks (b=<value optimized out>,
ns=<value optimized out>) at ../../_clean/gcc/fortran/resolve.c:8885
#7  0x000000010009adc2 in resolve_code (code=<value optimized out>, ns=<value
optimized out>) at ../../_clean/gcc/fortran/resolve.c:9557
#8  0x000000010009dab4 in resolve_codes (ns=<value optimized out>) at
../../_clean/gcc/fortran/resolve.c:14411
#9  0x000000010008e1bd in gfc_resolve (ns=<value optimized out>) at
../../_clean/gcc/fortran/resolve.c:14439
#10 0x00000001000825db in gfc_parse_file () at
../../_clean/gcc/fortran/parse.c:4399
#11 0x00000001000c25c6 in gfc_be_parse_file () at
../../_clean/gcc/fortran/f95-lang.c:189
#12 0x000000010076ce94 in compile_file () at ../../_clean/gcc/toplev.c:543
#13 0x000000010076ef69 in toplev_main (argc=2, argv=0x7fff5fbfd7c8) at
../../_clean/gcc/toplev.c:1864
#14 0x0000000100009b54 in start (pc=<value optimized out>, bases=0x0) at
../../../_clean/libgcc/config/unwind-dw2-fde-darwin.c:272


  reply	other threads:[~2013-04-06  9:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 23:12 [Bug fortran/56852] New: " bugs at stellardeath dot org
2013-04-06  9:33 ` dominiq at lps dot ens.fr [this message]
2013-04-07 11:48 ` [Bug fortran/56852] [4.6/4.7/4.8/4.9 Regression] " mikael at gcc dot gnu.org
2013-05-15 13:27 ` [Bug fortran/56852] [4.7/4.8/4.9 " rguenth at gcc dot gnu.org
2014-06-12 13:41 ` [Bug fortran/56852] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:25 ` [Bug fortran/56852] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-02-18 13:29 ` dominiq at lps dot ens.fr
2015-04-09  7:41 ` pault at gcc dot gnu.org
2015-06-23  8:15 ` [Bug fortran/56852] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 19:52 ` [Bug fortran/56852] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:26 ` jakub at gcc dot gnu.org
2015-10-19  5:07 ` [Bug fortran/56852] [4.9 " pault at gcc dot gnu.org
2015-10-19 19:33 ` pault at gcc dot gnu.org
2015-10-19 19:36 ` pault 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-56852-4-wHdvucmgNv@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).