public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34722] compile results in "internal compiler error: segmentation fault" message
Date: Wed, 09 Jan 2008 07:58:00 -0000	[thread overview]
Message-ID: <20080109073957.7385.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34722-14147@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from burnus at gcc dot gnu dot org  2008-01-09 07:39 -------
I don't get an segfault, but:
gamsana1.f90:1550.6:
      SUBROUTINE INVENTNAMES(ROWNAM, COLNAM, RNAMLEN, CNAMLEN, M, N)
     1
Reduced test case:


      PROGRAM GAMSANAL
      IMPLICIT NONE
      INTEGER(4), ALLOCATABLE, DIMENSION(:) :: namI
      CHARACTER,  ALLOCATABLE, DIMENSION(:) :: namC
      INTEGER IODICT, PROWNAM, PCOLNAM, PRNLEN, PCNLEN, M, N
      LOGICAL DICEXIST

      INQUIRE(UNIT=IODICT, EXIST=DICEXIST)
      CALL INVENTNAMES(namC(PROWNAM), M, N)
end

      SUBROUTINE INVENTNAMES(ROWNAM, M, N)
      IMPLICIT NONE
      INTEGER M,N
      CHARACTER ROWNAM(16,M)
      INTEGER RNAMLEN(M)
      END SUBROUTINE

Removing the "N" argument, crashes GCC here; valgrind shows a huge number of
invalid reads, starting with:

==16951== Invalid read of size 1
==16951==    at 0x473909: gfc_undo_symbols (symbol.c:2582)
==16951==    by 0x452454: decode_statement (parse.c:122)
==16951==    by 0x4530C4: next_statement (parse.c:505)
==16951==    by 0x4563B1: gfc_parse_file (parse.c:3317)
==16951==    by 0x47EF04: gfc_be_parse_file (f95-lang.c:260)
==16951==    by 0x6F2314: toplev_main (toplev.c:1042)
==16951==    by 0x52CEB29: (below main) (in /lib64/libc-2.6.1.so)


The reduced program works woth gfortran 4.2, which makes it a regression. (The
full program does not as %VAL is not supported by 4.2.)


-- 

burnus at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |burnus at gcc dot gnu dot
                   |                            |org


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


  parent reply	other threads:[~2008-01-09  7:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09  2:37 [Bug fortran/34722] New: " sdirkse at gams dot com
2008-01-09  3:15 ` [Bug fortran/34722] " sdirkse at gams dot com
2008-01-09  3:19 ` sdirkse at gams dot com
2008-01-09  7:58 ` burnus at gcc dot gnu dot org [this message]
2008-01-09  8:08 ` burnus at gcc dot gnu dot org
2008-01-09 10:35 ` dominiq at lps dot ens dot fr
2008-01-09 12:45 ` burnus at gcc dot gnu dot org
2008-01-09 14:18 ` dominiq at lps dot ens dot fr
2008-01-09 16:42 ` [Bug fortran/34722] [4.3 Regression] ICE: left-over "@iostat" variable polutes namespace burnus at gcc dot gnu dot org
2008-01-11  8:59 ` jvdelisle at gcc dot gnu dot org
2008-01-11 21:24 ` jvdelisle at gcc dot gnu dot org
2008-01-11 21:30 ` jvdelisle at gcc dot gnu dot org
2008-01-11 21:31 ` jvdelisle at gcc dot gnu dot org
2008-01-12  8:48 ` jvdelisle at gcc dot gnu dot org
2008-01-12  9:15 ` jvdelisle 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=20080109073957.7385.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).