public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/45673] New: -fcompare-debug failure with minor difference in dumps
Date: Tue, 14 Sep 2010 23:40:00 -0000 [thread overview]
Message-ID: <bug-45673-14164@http.gcc.gnu.org/bugzilla/> (raw)
Command line:
$ gcc -O3 -fcompare-debug -march=amdfam10 ada-langn.i
or
$ gcc -O2 -fcompare-debug -finline-functions -fipa-cp-clone
-fkeep-inline-functions ada-langn.i
(I am not able to reproduce it with these flags anymore)
or
$ gcc -O1 -fgcse -finline-small-functions -foptimize-sibling-calls -ftree-pre
-ftree-switch-conversion -ftree-vrp -fpartial-inlining -finline-functions
-fkeep-inline-functions -fcompare-debug ada-langn.i
The difference in dumps is small:
$ diff *gkd
107804c107804
< (const_int 32 [0x20])) [ MEM[(struct type *)0B].main_type+0
S8 A64])) ada-langn.i:15638# {*movdi_internal_rex64}
---
> (const_int 32 [0x20])) [ 0B->main_type+0 S8 A64])) ada-langn.i:15638# {*movdi_internal_rex64}
"MEM[(struct type *)0B]." <=> "0B->"
Tested revision:
r164287 - fail
r164280 - fail
r164228 - fail
--
Summary: -fcompare-debug failure with minor difference in dumps
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: zsojka at seznam dot cz
GCC host triplet: x86_64-pc-linux-gnu
GCC target triplet: x86_64-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45673
next reply other threads:[~2010-09-14 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 23:40 zsojka at seznam dot cz [this message]
2010-09-14 23:43 ` [Bug debug/45673] " zsojka at seznam dot cz
2010-09-15 9:49 ` rguenth at gcc dot gnu dot org
2010-09-21 8:02 ` aoliva at gcc dot gnu dot org
2010-09-21 8:53 ` aoliva 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=bug-45673-14164@http.gcc.gnu.org/bugzilla/ \
--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).