public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Eric.Diaz.Fernandez at eurid dot eu" <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: Tue, 11 Jun 2024 10:21:00 +0000 [thread overview] Message-ID: <bug-80379-4-DgIL1zvirG@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 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?
next prev parent reply other threads:[~2024-06-11 10:21 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 2024-06-11 10:21 ` Eric.Diaz.Fernandez at eurid dot eu [this message] 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-DgIL1zvirG@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).