public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/35045] [4.3 Regression] gcc-4.3 generates wrong code on i386 with -O3
Date: Fri, 01 Feb 2008 13:04:00 -0000 [thread overview]
Message-ID: <20080201130400.25673.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35045-8932@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from rguenth at gcc dot gnu dot org 2008-02-01 13:04 -------
gcse-after-reload inserts
(insn 66 30 31 3 (set (reg:SF 1 dx [+4 ])
(mem/c:SF (plus:SI (reg/f:SI 6 bp)
(const_int -16 [0xfffffffffffffff0])) [0 res$imag+0 S4 A]
on the edge from bb3 to bb4, which looks correct. This insn vanishes during
184r.dse2:
DCE: Deleting insn 66
deleting insn with uid = 66.
One problem may be that gcse doesn't update LIFE:
...
(insn 30 60 66 3 test-cacoshf.c:13 (parallel [
(asm_operands/v ("") ("") 0 []
[] 1606)
(clobber (reg:QI 18 fpsr))
(clobber (reg:QI 17 flags))
(clobber (reg:QI 5 di))
(clobber (reg:QI 4 si))
(clobber (reg:QI 3 bx))
(clobber (reg:QI 2 cx))
]) -1 (nil))
(insn 66 30 31 3 (set (reg:SF 1 dx [+4 ])
(mem/c:SF (plus:SI (reg/f:SI 6 bp)
(const_int -16 [0xfffffffffffffff0])) [0 res$imag+0 S4 A8])) -1
(nil))
;; End of basic block 3 -> ( 4)
;; lr out 6 [bp] 7 [sp] 9 [st(1)] 20 [frame]
lr out doesn't include dx. Is gcse supposed to update lr out?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35045
next prev parent reply other threads:[~2008-02-01 13:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 22:57 [Bug c/35045] New: " aurelien at aurel32 dot net
2008-01-31 22:59 ` [Bug c/35045] " aurelien at aurel32 dot net
2008-01-31 23:00 ` [Bug middle-end/35045] " pinskia at gcc dot gnu dot org
2008-01-31 23:11 ` [Bug c/35045] " aurelien at aurel32 dot net
2008-01-31 23:17 ` aurelien at aurel32 dot net
2008-02-01 10:34 ` [Bug target/35045] [4.3 Regression] " rguenth at gcc dot gnu dot org
2008-02-01 10:46 ` ismail at pardus dot org dot tr
2008-02-01 10:55 ` rguenth at gcc dot gnu dot org
2008-02-01 11:51 ` stevenb dot gcc at gmail dot com
2008-02-01 11:54 ` steven at gcc dot gnu dot org
2008-02-01 11:59 ` rguenth at gcc dot gnu dot org
2008-02-01 12:03 ` rguenth at gcc dot gnu dot org
2008-02-01 12:54 ` rguenth at gcc dot gnu dot org
2008-02-01 13:04 ` rguenth at gcc dot gnu dot org [this message]
2008-02-01 13:16 ` rguenth at gcc dot gnu dot org
2008-02-01 13:19 ` steven at gcc dot gnu dot org
2008-02-01 14:09 ` rguenth at gcc dot gnu dot org
2008-02-01 14:14 ` rguenth at gcc dot gnu dot org
2008-02-01 14:14 ` stevenb dot gcc at gmail dot com
2008-02-01 14:39 ` rguenther at suse dot de
2008-02-01 14:41 ` matz at gcc dot gnu dot org
2008-02-01 14:46 ` matz at gcc dot gnu dot org
2008-02-01 14:56 ` stevenb dot gcc at gmail dot com
2008-02-01 15:00 ` matz at gcc dot gnu dot org
2008-02-01 15:10 ` steven at gcc dot gnu dot org
2008-02-01 18:54 ` debian-gcc at lists dot debian dot org
2008-02-02 15:02 ` matz at gcc dot gnu dot org
2008-02-02 15:06 ` matz at gcc dot gnu dot org
2008-02-03 8:42 ` dominiq at lps dot ens dot fr
2008-02-03 11:29 ` ubizjak 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=20080201130400.25673.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).