public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matt at godbolt dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106020] Spurious warnings about stringop overflows only with LTO Date: Sat, 18 Jun 2022 14:02:08 +0000 [thread overview] Message-ID: <bug-106020-4-8FgrR2zraE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106020-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106020 --- Comment #6 from Matt Godbolt <matt at godbolt dot org> --- I'm afraid to say I've been unable to make a repro case in the short time I had to try - will get back to this but about to go on vacation (!). That's to say dumping the files from CE and using: CXX=/opt/compiler-explorer/gcc-12.1.0/bin/g++ CXXFLAGS=-O3 -flto -fno-fat-lto-objects -fPIC app: main.o date.o $(CXX) $(CXXFLAGS) -o app date.o main.o main.o: $(CXX) $(CXXFLAGS) -o main.o -c main.cpp date.o: $(CXX) $(CXXFLAGS) -o date.o -c date.cpp clean: rm -f app main.o date.o did _not_ cause the problem, so there's something else going on. Again, will try and get to this later, but apologies for the "hit and run" bug report :(
next prev parent reply other threads:[~2022-06-18 14:02 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-17 21:05 [Bug lto/106020] New: " matt at godbolt dot org 2022-06-17 21:06 ` [Bug lto/106020] " matt at godbolt dot org 2022-06-17 21:07 ` matt at godbolt dot org 2022-06-18 5:15 ` [Bug tree-optimization/106020] " pinskia at gcc dot gnu.org 2022-06-18 5:21 ` pinskia at gcc dot gnu.org 2022-06-18 13:45 ` matt at godbolt dot org 2022-06-18 14:02 ` matt at godbolt dot org [this message] 2023-05-18 2:57 ` pinskia at gcc dot gnu.org 2023-05-18 2:58 ` [Bug tree-optimization/106020] Spurious warnings about stringop overflows with -march=skylake -O3 pinskia at gcc dot gnu.org 2023-05-18 3:29 ` pinskia at gcc dot gnu.org 2023-05-18 3:40 ` pinskia at gcc dot gnu.org 2023-05-18 3:43 ` pinskia at gcc dot gnu.org 2023-05-18 3:58 ` pinskia at gcc dot gnu.org 2023-05-18 13:23 ` matt at godbolt 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-106020-4-8FgrR2zraE@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).