public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/98508] Sanitizer disable -Wall and -Wextra
Date: Tue, 05 Jan 2021 19:00:36 +0000	[thread overview]
Message-ID: <bug-98508-4-bsS1Ot2XEI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98508-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98508

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
It is not simple at all.  While the ifns don't modify the references variable,
they do modify the corresponding shadow memory, which is something GCC aliasing
oracle doesn't track at all, so by supplying detailed fnspec about the ifns
there is a very high risk it will start miscompiling things.
I have tried it in the past, and it just didn't work.

  parent reply	other threads:[~2021-01-05 19:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04  8:31 [Bug c++/98508] New: " awdawdawdawq123123 at gmx dot de
2021-01-04  8:51 ` [Bug c++/98508] " jakub at gcc dot gnu.org
2021-01-04  8:59 ` awdawdawdawq123123 at gmx dot de
2021-01-05 18:46 ` [Bug middle-end/98508] " msebor at gcc dot gnu.org
2021-01-05 19:00 ` jakub at gcc dot gnu.org [this message]
2021-01-05 20:02 ` msebor at gcc dot gnu.org
2021-04-16 22:32 ` msebor 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-98508-4-bsS1Ot2XEI@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).