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 sanitizer/65004] New: Compare debug failure with -fno-sanitize-recover -fsanitize=address -fsanitize=undefined Date: Tue, 10 Feb 2015 16:06:00 -0000 [thread overview] Message-ID: <bug-65004-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65004 Bug ID: 65004 Summary: Compare debug failure with -fno-sanitize-recover -fsanitize=address -fsanitize=undefined Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org Created attachment 34714 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34714&action=edit test.ii (compile with: g++ -fcompare-debug -O1 -fsanitize=address -fno-sanitize-recover -fsanitize=undefined) The attached program fails with g++: error: test.ii: -fcompare-debug failure when compiled with g++ -fcompare-debug -O1 -fsanitize=address -fno-sanitize-recover -fsanitize=undefined test.ii
next reply other threads:[~2015-02-10 16:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-10 16:06 burnus at gcc dot gnu.org [this message] 2015-02-10 16:23 ` [Bug sanitizer/65004] " jakub at gcc dot gnu.org 2015-02-10 18:00 ` jakub at gcc dot gnu.org 2015-02-10 22:00 ` jakub at gcc dot gnu.org 2015-02-10 22:01 ` [Bug sanitizer/65004] [5 Regression] " 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-65004-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: linkBe 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).