public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/80379] Redundant  note: code may be misoptimized unless -fno-strict-aliasing is used
Date: Mon, 09 Nov 2020 07:30:30 +0000	[thread overview]
Message-ID: <bug-80379-4-nsrWjnqOj8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-80379-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
The problem here is that the hint is output at decl merging and
-fno-strict-aliasing is a function local flag. At that time we do not even know
what functions will be since units are not streamed in yet.  This means that we
do not know if some unit has function that is -fno-strict-aliasing. So
supressing the warning does not fit the implementation very easily :(

       reply	other threads:[~2020-11-09  7:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-80379-4@http.gcc.gnu.org/bugzilla/>
2020-11-09  7:30 ` hubicka at gcc dot gnu.org [this message]
2024-06-11 10:21 ` Eric.Diaz.Fernandez at eurid dot eu
2024-06-11 15:26 ` andi-gcc at firstfloor 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-80379-4-nsrWjnqOj8@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).