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/45408] New: -fcompare-debug failure with -O2 -ftree-vectorize -fno-var-tracking-assignments
Date: Wed, 25 Aug 2010 20:54:00 -0000 [thread overview]
Message-ID: <bug-45408-14164@http.gcc.gnu.org/bugzilla/> (raw)
Compiler output:
$ gcc -fcompare-debug -O2 -ftree-vectorize -fno-var-tracking-assignments
testcase-min3i.ii
gcc: error: testcase-min3i.ii: -fcompare-debug failure
The difference is:
$ diff testcase-min3i.*gkd
439c439
< (mem/s/c:DI (symbol_ref:DI ("_economy") [flags 0x2] <var_decl #
_economy>) [ MEM[(struct OverflowSafeInt *)&_economy].max_loan.m_value+0 S8
A128])) /usr/include/sys/select.h:485# {*movdi_internal_rex64}
---
> (mem/s/c:DI (symbol_ref:DI ("_economy") [flags 0x2] <var_decl # _economy>) [ MEM[(struct OverflowSafeInt &)&_economy].max_loan.m_value+0 S8 A128])) /usr/include/sys/select.h:485# {*movdi_internal_rex64}
--
Summary: -fcompare-debug failure with -O2 -ftree-vectorize -fno-
var-tracking-assignments
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=45408
next reply other threads:[~2010-08-25 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 20:54 zsojka at seznam dot cz [this message]
2010-08-25 20:56 ` [Bug debug/45408] " zsojka at seznam dot cz
2010-08-30 8:53 ` aoliva at gcc dot gnu dot org
2010-08-30 10:59 ` zsojka at seznam dot cz
2010-09-04 15:27 ` aoliva at gcc dot gnu dot org
2010-09-08 21:54 ` aoliva at gcc dot gnu dot org
2010-09-13 3:42 ` 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-45408-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).