public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldot at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/29537] ICE in gfc_match_common
Date: Sat, 21 Oct 2006 18:05:00 -0000	[thread overview]
Message-ID: <20061021180538.5318.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29537-11811@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from aldot at gcc dot gnu dot org  2006-10-21 18:05 -------
(In reply to comment #2)
> (In reply to comment #1)
> > Shorter testcase:
> > $ egrep -v "(^\!|^$)" foo2.f90
> > block data
> >   common c
> > end
> > 
> According to lahey's checker, this code is valid. Still it ICEs

Program received signal SIGSEGV, Segmentation fault.
0x080b0982 in gfc_trans_common (ns=0x85e2f20)
    at ../../../src/gcc-4.2/gcc/fortran/trans-common.c:1059
1059          c->where = ns->proc_name->declared_at;
(gdb) bt
#0  0x080b0982 in gfc_trans_common (ns=0x85e2f20)
    at ../../../src/gcc-4.2/gcc/fortran/trans-common.c:1059
#1  0x080b15a4 in gfc_generate_block_data (ns=0x85e2f20)
    at ../../../src/gcc-4.2/gcc/fortran/trans-decl.c:3316
#2  0x08086b25 in gfc_parse_file ()
    at ../../../src/gcc-4.2/gcc/fortran/parse.c:3237
#3  0x080a5db9 in gfc_be_parse_file (set_yydebug=0)
    at ../../../src/gcc-4.2/gcc/fortran/f95-lang.c:303
#4  0x082f5d6d in toplev_main (argc=15, argv=0xaffe1ad4)
    at ../../../src/gcc-4.2/gcc/toplev.c:1033
#5  0x080cffe6 in main (argc=Cannot access memory at address 0x0
) at ../../../src/gcc-4.2/gcc/main.c:35


-- 


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


  parent reply	other threads:[~2006-10-21 18:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-21 17:32 [Bug fortran/29537] New: " aldot at gcc dot gnu dot org
2006-10-21 17:42 ` [Bug fortran/29537] " aldot at gcc dot gnu dot org
2006-10-21 18:04 ` aldot at gcc dot gnu dot org
2006-10-21 18:05 ` aldot at gcc dot gnu dot org [this message]
2006-10-21 18:49 ` aldot at gcc dot gnu dot org
2006-10-21 18:57 ` pinskia at gcc dot gnu dot org
2006-10-21 22:04 ` kargl at gcc dot gnu dot org
2006-10-22 11:36 ` [Bug fortran/29537] ICE in gfc_match_common for blank common in BLOCK DATA unit aldot at gcc dot gnu dot org
2006-10-22 11:50 ` aldot at gcc dot gnu dot org
2006-10-22 15:00 ` sgk at troutmask dot apl dot washington dot edu
2006-10-22 21:08 ` aldot at gcc dot gnu dot org
2006-10-26 12:59 ` aldot at gcc dot gnu dot org
2006-10-28 23:56 ` sgk at troutmask dot apl dot washington dot edu
2006-10-31 23:39 ` aldot at gcc dot gnu dot org
2006-10-31 23:42 ` aldot at gcc dot gnu dot org
2006-10-31 23:47 ` sgk at troutmask dot apl dot washington dot edu
2006-11-01 19:30 ` aldot at gcc dot gnu dot org
2006-11-30 19:26 ` chaoyingfu at gcc dot gnu dot 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=20061021180538.5318.qmail@sourceware.org \
    --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).