public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/37106] [4.4 Regression] ICE: in mems_in_disjoint_alias_sets_p, at alias.c:278
Date: Mon, 13 Oct 2008 16:55:00 -0000 [thread overview]
Message-ID: <20081013165420.20979.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37106-12313@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from dominiq at lps dot ens dot fr 2008-10-13 16:54 -------
> Can you try the failing test cases with -fno-PIC to see if these issues are
> related to the fact that darwin defaults to -fPIC?
Apparently the tests pass with -fno-PIC in 32 bit mode but not with -m64:
[ibook-dhum] f90/bug% gfc -c -O1 -msse2 -mfpmath=sse -march=k8 -fno-PIC
/opt/gcc/_gcc_clean/gcc/testsuite/gcc.target/i386/opt-1.c
[ibook-dhum] f90/bug% gfc -c -O1 -msse2 -mfpmath=sse -march=k8 -fno-PIC
/opt/gcc/_gcc_clean/gcc/testsuite/gcc.target/i386/opt-2.c
[ibook-dhum] f90/bug% gfc -m64 -c -O1 -msse2 -mfpmath=sse -march=k8 -fno-PIC
/opt/gcc/_gcc_clean/gcc/testsuite/gcc.target/i386/opt-1.c
/opt/gcc/_gcc_clean/gcc/testsuite/gcc.target/i386/opt-1.c: In function
'not_opt3':
/opt/gcc/_gcc_clean/gcc/testsuite/gcc.target/i386/opt-1.c:34: internal compiler
error: in mems_in_disjoint_alias_sets_p, at alias.c:278
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
[ibook-dhum] f90/bug% gfc -m64 -c -O1 -msse2 -mfpmath=sse -march=k8 -fno-PIC
/opt/gcc/_gcc_clean/gcc/testsuite/gcc.target/i386/opt-2.c
/opt/gcc/_gcc_clean/gcc/testsuite/gcc.target/i386/opt-2.c: In function
'not_opt3':
/opt/gcc/_gcc_clean/gcc/testsuite/gcc.target/i386/opt-2.c:37: internal compiler
error: in mems_in_disjoint_alias_sets_p, at alias.c:278
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37106
next prev parent reply other threads:[~2008-10-13 16:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 7:39 [Bug c/37106] New: " dominiq at lps dot ens dot fr
2008-08-13 10:04 ` [Bug c/37106] [4.4 Regression] " rguenth at gcc dot gnu dot org
2008-08-22 15:29 ` rguenth at gcc dot gnu dot org
2008-08-27 9:27 ` dominiq at lps dot ens dot fr
2008-10-13 8:56 ` dominiq at lps dot ens dot fr
2008-10-13 13:47 ` howarth at nitro dot med dot uc dot edu
2008-10-13 14:00 ` dominiq at lps dot ens dot fr
2008-10-13 14:14 ` howarth at nitro dot med dot uc dot edu
2008-10-13 14:25 ` dominiq at lps dot ens dot fr
2008-10-13 16:12 ` howarth at nitro dot med dot uc dot edu
2008-10-13 16:55 ` dominiq at lps dot ens dot fr [this message]
2008-10-14 8:12 ` ghazi at gcc dot gnu dot org
2008-10-14 10:16 ` dominiq at lps dot ens dot fr
2008-10-14 10:58 ` [Bug c/37106] [4.4 Regression] ICE with -fpic or -fPIC: " dominiq at lps dot ens dot fr
2008-10-15 18:39 ` ghazi at gcc dot gnu dot org
2008-10-15 18:56 ` dominiq at lps dot ens dot fr
2008-10-15 19:00 ` dominiq at lps dot ens dot fr
2008-10-15 21:07 ` hjl dot tools at gmail dot com
2008-11-03 15:40 ` jakub at gcc dot gnu dot org
2008-11-04 20:09 ` jakub at gcc dot gnu dot org
2008-11-04 20:25 ` jakub at gcc dot gnu dot org
2008-11-11 0:54 ` pinskia 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=20081013165420.20979.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).