public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/37243] [4.4 Regression] IRA causes wrong code generation Date: Wed, 03 Sep 2008 16:06:00 -0000 [thread overview] Message-ID: <20080903160503.11301.qmail@sourceware.org> (raw) In-Reply-To: <bug-37243-682@http.gcc.gnu.org/bugzilla/> ------- Comment #22 from hjl dot tools at gmail dot com 2008-09-03 16:05 ------- (In reply to comment #7) > Created an attachment (id=16155) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16155&action=view) [edit] > Test case from 2006.434.zeusmp > > Though fail to extract a smaller case, hopeful it helpful. > > Compile with gfortran -c -O2 -DSPEC_CPU_LP64 tranx1.f -S -fdump-rtl-all -g. > Miscompile in revision 139590. > > In IRA dump file, I believe following suspicious RTL is the cause of segfault: > (insn 886 885 893 35 tranx1.f:570 (set (reg:DI 0 ax [orig:123 D.3215 ] [123]) > (mem/c:DI (plus:DI (reg/f:DI 7 sp) > (const_int -104 [0xffffffffffffff98])) [68 D.3215+0 S8 A64])) > 89 {*movdi_1_rex64} (nil)) > > (insn 893 886 896 35 tranx1.f:570 (set (mem/c:DI (plus:DI (reg/f:DI 7 sp) > (const_int -104 [0xffffffffffffff98])) [68 ivtmp.160+0 S8 A64]) > (reg/f:DI 3 bx [orig:159 ivtmp.160 ] [159])) 89 {*movdi_1_rex64} (nil)) > D.3215 and ivtmp.160 shares the spill space (%rsp-104), where as D.3215 and > ivtmp.160 has overlapped liverange. > It is fixed by Richard's use DF patch: http://gcc.gnu.org/ml/gcc/2008-09/msg00015.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37243
next prev parent reply other threads:[~2008-09-03 16:06 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-08-26 15:01 [Bug middle-end/37243] New: [4.4 Regression] Revision 139590 caused many regressions hjl dot tools at gmail dot com 2008-08-26 15:08 ` [Bug middle-end/37243] " hjl dot tools at gmail dot com 2008-08-26 15:38 ` rguenth at gcc dot gnu dot org 2008-08-26 18:23 ` hjl dot tools at gmail dot com 2008-08-26 20:04 ` hjl dot tools at gmail dot com 2008-08-26 20:11 ` hjl dot tools at gmail dot com 2008-08-26 20:46 ` pinskia at gcc dot gnu dot org 2008-08-26 22:25 ` hjl dot tools at gmail dot com 2008-08-27 0:06 ` hjl dot tools at gmail dot com 2008-08-27 8:09 ` Joey dot ye at intel dot com 2008-08-27 8:12 ` Joey dot ye at intel dot com 2008-08-27 13:28 ` dominiq at lps dot ens dot fr 2008-08-27 16:35 ` vmakarov at redhat dot com 2008-08-28 6:16 ` Joey dot ye at intel dot com 2008-08-29 4:39 ` [Bug middle-end/37243] [4.4 Regression] IRA causes wrong code generation pinskia at gcc dot gnu dot org 2008-08-29 15:56 ` vmakarov at redhat dot com 2008-08-29 16:19 ` vmakarov at gcc dot gnu dot org 2008-08-29 18:25 ` hjl dot tools at gmail dot com 2008-08-29 19:48 ` pinskia at gcc dot gnu dot org 2008-08-30 18:53 ` vmakarov at redhat dot com 2008-09-02 18:18 ` hjl at gcc dot gnu dot org 2008-09-02 18:25 ` hjl at gcc dot gnu dot org 2008-09-02 18:30 ` hjl at gcc dot gnu dot org 2008-09-02 20:41 ` hjl dot tools at gmail dot com 2008-09-02 23:53 ` hjl dot tools at gmail dot com 2008-09-03 16:06 ` hjl dot tools at gmail dot com [this message] 2008-09-03 19:46 ` hjl dot tools at gmail dot com 2008-09-03 20:05 ` hjl dot tools at gmail dot com 2008-09-03 20:15 ` vmakarov at gcc dot gnu dot org 2008-09-03 20:23 ` vmakarov at gcc dot gnu dot org 2008-09-04 5:02 ` hjl at gcc dot gnu dot org 2008-09-04 5:47 ` hjl dot tools at gmail dot com 2008-09-04 13:36 ` hjl dot tools at gmail dot com 2008-09-04 15:48 ` hjl at gcc dot gnu dot org 2008-09-04 18:50 ` rsandifo at gcc dot gnu dot org 2008-09-04 21:06 ` hjl dot tools at gmail dot com
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=20080903160503.11301.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).