public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aovb94 at dsl dot pipex dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/28788] [gfortran: 4.1, 4.2 regression] ICE on valid code Date: Sat, 26 Aug 2006 12:15:00 -0000 [thread overview] Message-ID: <20060826121515.18452.qmail@sourceware.org> (raw) In-Reply-To: <bug-28788-2736@http.gcc.gnu.org/bugzilla/> ------- Comment #13 from aovb94 at dsl dot pipex dot com 2006-08-26 12:15 ------- I'm getting an ICE and segmentation fault in the following code. I think it may be related to Paul Thomas's observation about pointers to components of derived type arrays. However, it does compile under these circumstances: * when foo and bar are not in the module * when the module contains foo or bar but not both * when the types a and b have no reference to each other * when ", only, a (or b)" is not used on the use statement MODULE type_mod TYPE a INTEGER :: n(10) END TYPE a ! TYPE b TYPE (a), POINTER :: m(:) => NULL () END TYPE b END MODULE type_mod MODULE seg_mod CONTAINS SUBROUTINE foo (x) USE type_mod, ONLY : a ! fails ! USE type_mod ! works IMPLICIT NONE TYPE (a) :: x ! RETURN END SUBROUTINE foo ! SUBROUTINE bar (x) USE type_mod, ONLY : b ! fails ! USE type_mod ! works IMPLICIT NONE TYPE (b) :: x ! RETURN END SUBROUTINE bar END MODULE seg_mod gfc -c type_mod.f95 seg_mod.f95 seg_mod.f95:0: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. gfc -v Using built-in specs. Target: x86_64-unknown-linux-gnu Configured with: ../gcc/configure --enable-languages=c,fortran --prefix=/home/martin/GCC/usr/local --disable-nls --disable-multilib --enable-shared --enable-threads=posix --disable-checking --enable-long-long --enable-__cxa_atexit --enable-clocale=gnu --disable-libunwind-exception Thread model: posix gcc version 4.2.0 20060825 (experimental) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28788
next prev parent reply other threads:[~2006-08-26 12:15 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-08-21 11:37 [Bug fortran/28788] New: " martin at mpa-garching dot mpg dot de 2006-08-22 5:30 ` [Bug fortran/28788] " pault at gcc dot gnu dot org 2006-08-22 20:02 ` pault at gcc dot gnu dot org 2006-08-23 13:20 ` paul dot richard dot thomas at cea dot fr 2006-08-23 14:51 ` patchapp at dberlin dot org 2006-08-24 4:47 ` pault at gcc dot gnu dot org 2006-08-24 4:54 ` pault at gcc dot gnu dot org 2006-08-25 12:57 ` martin at mpa-garching dot mpg dot de 2006-08-25 13:25 ` paulthomas2 at wanadoo dot fr 2006-08-25 14:36 ` martin at mpa-garching dot mpg dot de 2006-08-25 14:37 ` martin at mpa-garching dot mpg dot de 2006-08-25 17:09 ` jvdelisle at gcc dot gnu dot org 2006-08-26 9:30 ` paulthomas2 at wanadoo dot fr 2006-08-26 12:15 ` aovb94 at dsl dot pipex dot com [this message] 2006-08-26 21:27 ` jvdelisle at gcc dot gnu dot org 2006-08-28 11:57 ` paul dot richard dot thomas at cea dot fr 2006-08-29 4:51 ` pault at gcc dot gnu dot org 2006-08-29 4:57 ` pault at gcc dot gnu dot org 2006-08-30 4:37 ` pault 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=20060826121515.18452.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: linkBe 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).