public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "KnowlesPJ at Cardiff dot ac dot uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/35892] New: gfortran dies on file containing module and common Date: Wed, 09 Apr 2008 17:24:00 -0000 [thread overview] Message-ID: <bug-35892-14459@http.gcc.gnu.org/bugzilla/> (raw) Compilation with -O0 -g causes the compiler to crash: /opt/gcc/bin/gfortran -c -fno-second-underscore -fdefault-integer-8 -m64 -g -O0 --save-temps f12_integrals.f f12_integrals.f: In function 'f12_integrals_raw': f12_integrals.f:980: internal compiler error: in expand_expr_real_1, at expr.c:7258 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Using built-in specs. Target: i386-apple-darwin9.2.2 Configured with: ../configure --prefix=/opt/gcc --enable-languages=c,fortran : (reconfigured) ../configure --prefix=/opt/gcc --enable-languages=c,fortran --no-create --no-recursion Thread model: posix gcc version 4.4.0 20080409 (experimental) (GCC) Although gcc -v reports 'i386' this is in fact an x86_64. But compiling on a true ia32 (and omitting -m64) produces the same crash. With -g removed or -O1 the compiler completes. However we are getting wrong results, so perhaps the place to start is with the crash and then try again? -- Summary: gfortran dies on file containing module and common Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: KnowlesPJ at Cardiff dot ac dot uk GCC host triplet: i386-apple-darwin9.2.2 GCC target triplet: i386-apple-darwin9.2.2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35892
next reply other threads:[~2008-04-09 17:24 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-09 17:24 KnowlesPJ at Cardiff dot ac dot uk [this message] 2008-04-09 17:25 ` [Bug fortran/35892] " KnowlesPJ at Cardiff dot ac dot uk 2008-04-09 18:32 ` [Bug fortran/35892] [4.4 regression] " burnus at gcc dot gnu dot org 2008-04-13 20:46 ` tkoenig at gcc dot gnu dot org 2008-04-18 14:42 ` jvdelisle at gcc dot gnu dot org 2008-04-18 15:10 ` jvdelisle at gcc dot gnu dot org 2008-04-18 16:24 ` jvdelisle at gcc dot gnu dot org 2008-04-18 17:13 ` kargl at gcc dot gnu dot org 2008-04-18 17:45 ` jvdelisle at gcc dot gnu dot org 2008-04-18 19:49 ` kargl at gcc dot gnu dot org 2008-04-18 21:28 ` jvdelisle at gcc dot gnu dot org 2008-04-18 21:32 ` jvdelisle at gcc dot gnu dot org 2008-04-19 0:08 ` kargl at gcc dot gnu dot org 2008-04-19 6:44 ` jvdelisle at gcc dot gnu dot org 2008-04-19 6:51 ` jvdelisle at gcc dot gnu dot org 2008-04-19 6:53 ` jvdelisle at gcc dot gnu dot org 2008-04-19 12:09 ` george at gcc dot gnu dot org 2008-04-19 21:12 ` [Bug fortran/35892] gfortran lost memory blocks jvdelisle at gcc dot gnu dot org 2008-04-24 8:30 ` george at gcc dot gnu dot org 2008-04-24 9:35 ` KnowlesPJ at Cardiff dot ac dot uk 2008-04-24 19:05 ` jvdelisle at gcc dot gnu dot org 2008-04-24 19:11 ` jvdelisle at gcc dot gnu dot org 2008-04-25 8:10 ` KnowlesPJ at Cardiff dot ac dot uk 2008-04-26 9:47 ` george at gcc dot gnu dot org 2008-04-26 10:19 ` george at gcc dot gnu dot org 2008-04-27 1:09 ` 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=bug-35892-14459@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: 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).