public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/64937] New: [5 Regression] compare debug failure with -fsanitize=address
Date: Wed, 04 Feb 2015 17:15:00 -0000 [thread overview]
Message-ID: <bug-64937-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64937
Bug ID: 64937
Summary: [5 Regression] compare debug failure with
-fsanitize=address
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: burnus at gcc dot gnu.org
Split-off from PR64935, which shows the same message but is caused by a
different revision.
The attached test case fails for me with
GCC_COMPARE_DEBUG=yes g++ test.ii -fsanitize=address
with the same message:
g++: error: test.ii: -fcompare-debug failure (length)
Test case is attachment 34664
Works with current 4.9 branch, fails with today's trunk and also with r220315
(the other PR, PR64935, works with that revision).
next reply other threads:[~2015-02-04 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 17:15 burnus at gcc dot gnu.org [this message]
2015-02-04 17:56 ` [Bug middle-end/64937] " burnus at gcc dot gnu.org
2015-02-04 21:11 ` jakub at gcc dot gnu.org
2015-02-05 11:16 ` jakub at gcc dot gnu.org
2015-02-05 12:00 ` jakub at gcc dot gnu.org
2015-02-06 8:59 ` jakub at gcc dot gnu.org
2015-02-06 18:27 ` jakub at gcc dot gnu.org
2015-02-06 18:32 ` jakub at gcc dot gnu.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-64937-4@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).