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 middle-end/34483] wo_prof_two_strs.c:56: internal compiler error: in find_new_var_of_type, at ipa-struct-reorg.c:605
Date: Mon, 21 Jan 2008 14:27:00 -0000 [thread overview]
Message-ID: <20080121140942.21500.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34483-276@http.gcc.gnu.org/bugzilla/>
------- Comment #40 from dominiq at lps dot ens dot fr 2008-01-21 14:09 -------
> Why are you running wo_prof_mult_field_peeling.c with profiling?
My best guess is because I have reused some previous command line(s) with it
(from gcc.dg/struct/w_prof_global_array.c for instance) without thinking about
it.
Anyway, I have run all the tests in gcc.dg/struct failing with
-m64 with -O3 -fipa-struct-reorg -fwhole-program -combine -fipa-type-escape
-m64
and they all crash with "Segmentation fault".
The backtrace for gcc.dg/struct/wo_prof_mult_field_peeling.c is:
Process: a.out [41283]
Path: a.out
Identifier: a.out
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: tcsh [11101]
Date/Time: 2008-01-21 15:03:26.935 +0100
OS Version: Mac OS X 10.5.1 (9B18)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000200a70
Crashed Thread: 0
Thread 0 Crashed:
0 a.out 0x0000000100000f40 main + 64
1 a.out 0x0000000100000ed4 start + 52
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000200a70 rbx: 0x0000000000000000 rcx: 0x0000000000000000
rdx: 0x0000000000000000
rdi: 0x00000001002fc095 rsi: 0x0000000000000000 rbp: 0x00007fff5fbfec10
rsp: 0x00007fff5fbfec10
r8: 0x00000001002fe01a r9: 0x0000000001000000 r10: 0x0000000003000001
r11: 0x00007fff8416e474
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000
r15: 0x0000000000000000
rip: 0x0000000100000f40 rfl: 0x0000000000010246 cr2: 0x0000000000200a70
Binary Images:
0x100000000 - 0x100000ff7 +a.out ??? (???)
/Volumes/MacBook/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out
0x100003000 - 0x1000c9fef +libgfortran.3.dylib ??? (???)
<ac0635c6511429acc90b895479c2cbb0>
/opt/gcc/gcc4.3w/lib/x86_64/libgfortran.3.dylib
0x10010d000 - 0x100120ff1 +libgcc_s.1.dylib ??? (???)
<e9505452e93d052d01993982f18fa20a> /opt/gcc/gcc4.3w/lib/libgcc_s.1.dylib
0x7fff5fc00000 - 0x7fff5fc2e3a3 dyld 95.3 (???)
<cd99d065ba4917450dca6958a854c594> /usr/lib/dyld
0x7fff819a9000 - 0x7fff819b5ff1 libgcc_s.1.dylib ??? (???)
<6fc905606335f261db4da9529c7e2711> /usr/lib/libgcc_s.1.dylib
0x7fff83fcd000 - 0x7fff83fcffff libmathCommon.A.dylib ??? (???)
/usr/lib/system/libmathCommon.A.dylib
0x7fff8416c000 - 0x7fff842ebfeb libSystem.B.dylib ??? (???)
<a9297f52cb1431e26cd3ffd4b9ca7615> /usr/lib/libSystem.B.dylib
0x7fffffe00000 - 0x7fffffe01780 libSystem.B.dylib ??? (???)
/usr/lib/libSystem.B.dylib
for gcc.dg/struct/wo_prof_two_strs.c
Process: a.out [41292]
Path: a.out
Identifier: a.out
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: tcsh [11101]
Date/Time: 2008-01-21 15:04:45.522 +0100
OS Version: Mac OS X 10.5.1 (9B18)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000809600
Crashed Thread: 0
Thread 0 Crashed:
0 a.out 0x0000000100000ed0 main + 256
1 a.out 0x0000000100000da4 start + 52
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x000000000080d600 rbx: 0x0000000000000fa0 rcx: 0x0000000100ff80d6
rdx: 0x0000000000000000
rdi: 0x0000000000809600 rsi: 0x00000000000003e8 rbp: 0x00007fff5fbfec10
rsp: 0x00007fff5fbfebf0
r8: 0x00000000034d2346 r9: 0x0000000000000000 r10: 0x0000000100002140
r11: 0x00007fff8416e474
r12: 0x000000010080a600 r13: 0x000000000080c600 r14: 0x0000000000000000
r15: 0x0000000000000000
rip: 0x0000000100000ed0 rfl: 0x0000000000010246 cr2: 0x0000000000809600
Binary Images:
0x100000000 - 0x100000fff +a.out ??? (???)
/Volumes/MacBook/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out
0x100003000 - 0x1000c9fef +libgfortran.3.dylib ??? (???)
<ac0635c6511429acc90b895479c2cbb0>
/opt/gcc/gcc4.3w/lib/x86_64/libgfortran.3.dylib
0x10010d000 - 0x100120ff1 +libgcc_s.1.dylib ??? (???)
<e9505452e93d052d01993982f18fa20a> /opt/gcc/gcc4.3w/lib/libgcc_s.1.dylib
0x7fff5fc00000 - 0x7fff5fc2e3a3 dyld 95.3 (???)
<cd99d065ba4917450dca6958a854c594> /usr/lib/dyld
0x7fff819a9000 - 0x7fff819b5ff1 libgcc_s.1.dylib ??? (???)
<6fc905606335f261db4da9529c7e2711> /usr/lib/libgcc_s.1.dylib
0x7fff83fcd000 - 0x7fff83fcffff libmathCommon.A.dylib ??? (???)
/usr/lib/system/libmathCommon.A.dylib
0x7fff8416c000 - 0x7fff842ebfeb libSystem.B.dylib ??? (???)
<a9297f52cb1431e26cd3ffd4b9ca7615> /usr/lib/libSystem.B.dylib
0x7fffffe00000 - 0x7fffffe01780 libSystem.B.dylib ??? (???)
/usr/lib/libSystem.B.dylib
and so on (I can give similar ones for the other cases). Note that if I remove
'-fipa-type-escape' the segfaults disappear (with unpatched rev. 131689).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34483
next prev parent reply other threads:[~2008-01-21 14:10 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 17:21 [Bug middle-end/34483] New: " danglin at gcc dot gnu dot org
2007-12-17 15:15 ` [Bug middle-end/34483] " olga at gcc dot gnu dot org
2007-12-24 2:08 ` dave at hiauly1 dot hia dot nrc dot ca
2007-12-28 14:58 ` rsandifo at gcc dot gnu dot org
2007-12-28 19:28 ` olga at gcc dot gnu dot org
2007-12-28 19:38 ` rsandifo at nildram dot co dot uk
2007-12-28 19:54 ` dave at hiauly1 dot hia dot nrc dot ca
2007-12-29 1:25 ` dave at hiauly1 dot hia dot nrc dot ca
2007-12-29 16:20 ` hjl at lucon dot org
2007-12-30 12:19 ` olga at gcc dot gnu dot org
2007-12-30 14:54 ` pinskia at gcc dot gnu dot org
2007-12-31 19:44 ` dominiq at lps dot ens dot fr
2008-01-02 13:24 ` rsandifo at nildram dot co dot uk
2008-01-02 15:16 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-02 17:26 ` dominiq at lps dot ens dot fr
2008-01-03 2:40 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-07 14:10 ` olga at gcc dot gnu dot org
2008-01-07 20:19 ` dominiq at lps dot ens dot fr
2008-01-08 16:11 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-15 14:55 ` olga at gcc dot gnu dot org
2008-01-15 20:50 ` dominiq at lps dot ens dot fr
2008-01-16 7:13 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-20 14:35 ` olga at gcc dot gnu dot org
2008-01-20 15:29 ` dominiq at lps dot ens dot fr
2008-01-20 18:10 ` olga at gcc dot gnu dot org
2008-01-20 19:27 ` dominiq at lps dot ens dot fr
2008-01-20 21:33 ` dominiq at lps dot ens dot fr
2008-01-21 14:10 ` olga at gcc dot gnu dot org
2008-01-21 14:27 ` dominiq at lps dot ens dot fr [this message]
2008-01-21 15:18 ` dominiq at lps dot ens dot fr
2008-01-21 19:10 ` olga at il dot ibm dot com
2008-01-21 19:56 ` dominiq at lps dot ens dot fr
2008-01-21 20:41 ` olga at il dot ibm dot com
2008-01-21 20:42 ` dominiq at lps dot ens dot fr
2008-01-21 20:55 ` olga at il dot ibm dot com
2008-01-21 21:43 ` dominiq at lps dot ens dot fr
2008-01-22 21:02 ` olga at il dot ibm dot com
2008-01-22 22:12 ` olga at il dot ibm dot com
2008-01-22 23:26 ` dominiq at lps dot ens dot fr
2008-01-22 23:42 ` olga at il dot ibm dot com
2008-01-22 23:50 ` dominiq at lps dot ens dot fr
2008-01-24 13:53 ` dominiq at lps dot ens dot fr
2008-01-24 16:43 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-25 0:34 ` danglin at gcc dot gnu dot org
2008-01-25 9:14 ` olga at il dot ibm dot com
2008-01-25 19:30 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-26 22:46 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-29 10:15 ` alond at il dot ibm dot com
2008-01-30 20:14 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-31 18:53 ` alond at il dot ibm dot com
2008-01-31 22:24 ` dave at hiauly1 dot hia dot nrc dot ca
2008-01-31 22:30 ` dave at hiauly1 dot hia dot nrc dot ca
2008-02-03 14:49 ` olga at gcc dot gnu dot org
2008-02-05 2:43 ` dave at hiauly1 dot hia dot nrc dot ca
2008-02-07 10:26 ` olga at gcc dot gnu dot org
2008-02-07 15:34 ` dave at hiauly1 dot hia dot nrc dot ca
2008-11-01 20:16 ` danglin 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=20080121140942.21500.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).