public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/99168] inconsistent behavior on -O0 and -O2 with ASAN on
Date: Mon, 22 Feb 2021 16:44:38 +0000 [thread overview]
Message-ID: <bug-99168-4-GgnrPLfTFh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99168-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99168
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to zhan3299 from comment #4)
> (In reply to Martin Liška from comment #3)
> > Very interesting issue, the failure is caused by IPA ICF that merges 2
> > variables with different alignments. I've got a patch candidate.
>
> Hi, just curious because I am also studying the source code of GCC.
>
> Is this issue is about sanitizer or optimization?
It's bad optimization done by IPA ICF. The issue is gone with -fno-ipa-icf.
next prev parent reply other threads:[~2021-02-22 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 16:44 [Bug c/99168] New: " zhan3299 at purdue dot edu
2021-02-19 16:57 ` [Bug c/99168] " zhan3299 at purdue dot edu
2021-02-22 9:45 ` [Bug sanitizer/99168] " marxin at gcc dot gnu.org
2021-02-22 15:07 ` marxin at gcc dot gnu.org
2021-02-22 16:13 ` zhan3299 at purdue dot edu
2021-02-22 16:44 ` marxin at gcc dot gnu.org [this message]
2021-02-23 15:03 ` cvs-commit at gcc dot gnu.org
2021-02-23 15:05 ` marxin 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-99168-4-GgnrPLfTFh@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).