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 debug/44971] [4.6 Regression] -fcompare-debug failure with uninitialized read in walk_gimple_stmt
Date: Sun, 18 Jul 2010 20:47:00 -0000 [thread overview]
Message-ID: <20100718204653.25584.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44971-14164@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from rguenth at gcc dot gnu dot org 2010-07-18 20:46 -------
@@ -29,7 +29,7 @@
(note# 0 0 NOTE_INSN_DELETED)
(note# 0 0 [bb 2] NOTE_INSN_BASIC_BLOCK)
(note# 0 0 NOTE_INSN_FUNCTION_BEG)
-(insn:TI# 0 0 pr44971.c:22 (set (reg/f:SI 0 ax [orig:58 D.xxxx ] [58])
+(insn:TI# 0 0 pr44971.c:22 (set (reg/v/f:SI 0 ax [orig:58 info ] [58])
(mem/f/c:SI (symbol_ref:SI ("_XftintInfo") <var_decl # _XftintInfo>)
[ MEM[(struct XftintInfo * *)&_XftintInfo]+0 S4 A32]))# {*movsi_internal}
(nil))
(insn/f:TI# 0 0 pr44971.c:20 (set (mem:SI (pre_dec:SI (reg/f:SI 7 sp)) [ S4
A8])
(reg/f:SI 6 bp))# {*pushsi2} (nil))
@@ -37,7 +37,7 @@
(reg/f:SI 7 sp))# {*movsi_internal} (nil))
(note# 0 0 NOTE_INSN_PROLOGUE_END)
(insn:TI# 0 0 pr44971.c:22 (set (reg:CCZ 17 flags)
- (compare:CCZ (reg/f:SI 0 ax [orig:58 D.xxxx ] [58])
+ (compare:CCZ (reg/v/f:SI 0 ax [orig:58 info ] [58])
(const_int 0 [0])))# {*cmpsi_ccno_1} (nil))
(jump_insn:TI# 0 0 pr44971.c:22 (set (pc)
(if_then_else (eq (reg:CCZ 17 flags)
...
caused by phiprop. It chooses one dereference result to choose the
result. But debug stmts change order of immediate uses.
With debug stmts (uses of prev_1):
# VUSE <.MEM_8(D)>
info_5 = *prev_1;
# DEBUG prev => prev_1
# VUSE <.MEM_8(D)>
D.1973_6 = *prev_1;
without:
# VUSE <.MEM_8(D)>
D.1973_6 = *prev_1;
# VUSE <.MEM_8(D)>
info_5 = *prev_1;
so relying on stable order of immediate uses is now wrong? The compare-debug
failure is spurious, there is no difference in the assembly output.
I can fix it by always degrading debug info and creating a new variable.
Alex, why should the immediate use lists show this behavior?
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aoliva at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44971
next prev parent reply other threads:[~2010-07-18 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-17 11:44 [Bug debug/44971] New: " zsojka at seznam dot cz
2010-07-17 11:46 ` [Bug debug/44971] " zsojka at seznam dot cz
2010-07-17 13:37 ` hjl dot tools at gmail dot com
2010-07-17 13:38 ` hjl dot tools at gmail dot com
2010-07-18 17:50 ` [Bug debug/44971] [4.6 Regression] " rguenth at gcc dot gnu dot org
2010-07-18 20:47 ` rguenth at gcc dot gnu dot org [this message]
2010-07-19 13:40 ` rguenth at gcc dot gnu dot org
2010-07-19 16:05 ` rguenth at gcc dot gnu dot org
2010-07-20 11:29 ` rguenth at gcc dot gnu dot org
2010-07-20 11:30 ` rguenth 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=20100718204653.25584.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).