public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug lto/80379] Redundant  note: code may be misoptimized unless -fno-strict-aliasing is used
       [not found] <bug-80379-4@http.gcc.gnu.org/bugzilla/>
@ 2020-11-09  7:30 ` hubicka at gcc dot gnu.org
  2024-06-11 10:21 ` Eric.Diaz.Fernandez at eurid dot eu
  2024-06-11 15:26 ` andi-gcc at firstfloor dot org
  2 siblings, 0 replies; 3+ messages in thread
From: hubicka at gcc dot gnu.org @ 2020-11-09  7:30 UTC (permalink / raw)
  To: gcc-bugs

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 :(

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug lto/80379] Redundant  note: code may be misoptimized unless -fno-strict-aliasing is used
       [not found] <bug-80379-4@http.gcc.gnu.org/bugzilla/>
  2020-11-09  7:30 ` [Bug lto/80379] Redundant note: code may be misoptimized unless -fno-strict-aliasing is used hubicka at gcc dot gnu.org
@ 2024-06-11 10:21 ` Eric.Diaz.Fernandez at eurid dot eu
  2024-06-11 15:26 ` andi-gcc at firstfloor dot org
  2 siblings, 0 replies; 3+ messages in thread
From: Eric.Diaz.Fernandez at eurid dot eu @ 2024-06-11 10:21 UTC (permalink / raw)
  To: gcc-bugs

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

Eric Diaz Fernandez <Eric.Diaz.Fernandez at eurid dot eu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |Eric.Diaz.Fernandez at eurid dot e
                   |                            |u

--- Comment #4 from Eric Diaz Fernandez <Eric.Diaz.Fernandez at eurid dot eu> ---
I believe I've hit that bug. I was about to post a report it when I found this
one.

When building one of my programs with -flto but without -fno-strict-aliasing
the resulting assembly misses the call to an initialization function.
The current workaround suggested to the maintainer is to not use -flto

Is there anything I can add to help fixing the issue?

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug lto/80379] Redundant  note: code may be misoptimized unless -fno-strict-aliasing is used
       [not found] <bug-80379-4@http.gcc.gnu.org/bugzilla/>
  2020-11-09  7:30 ` [Bug lto/80379] Redundant note: code may be misoptimized unless -fno-strict-aliasing is used hubicka at gcc dot gnu.org
  2024-06-11 10:21 ` Eric.Diaz.Fernandez at eurid dot eu
@ 2024-06-11 15:26 ` andi-gcc at firstfloor dot org
  2 siblings, 0 replies; 3+ messages in thread
From: andi-gcc at firstfloor dot org @ 2024-06-11 15:26 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #5 from Andi Kleen <andi-gcc at firstfloor dot org> ---
This bug is about printing a unnecessary message. If your code is actually
miscompiled even with -fno-strict-aliasing set (so it is ignored somewhere) it
is something different and you would need a test case to debug.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2024-06-11 15:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <bug-80379-4@http.gcc.gnu.org/bugzilla/>
2020-11-09  7:30 ` [Bug lto/80379] Redundant note: code may be misoptimized unless -fno-strict-aliasing is used hubicka at gcc dot gnu.org
2024-06-11 10:21 ` Eric.Diaz.Fernandez at eurid dot eu
2024-06-11 15:26 ` andi-gcc at firstfloor dot org

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).