public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/110515] New: [14 Regression] llvm-15.0.7 possibly invalid code on -O3 Date: Sat, 01 Jul 2023 21:52:54 +0000 [thread overview] Message-ID: <bug-110515-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110515 Bug ID: 110515 Summary: [14 Regression] llvm-15.0.7 possibly invalid code on -O3 Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: slyfox at gcc dot gnu.org Target Milestone: --- Created attachment 55447 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55447&action=edit DwarfCompileUnit.cpp Initially the failure is observed on r14-2233-gfca6d9c12f5bf0 where llvm-15.0.7 test suite fails a single test: Failed Tests (1): LLVM :: DebugInfo/X86/vla-multi.ll I think I shrunk it down to DwarfCompileUnit.cpp: $ g++ -std=c++14 DwarfCompileUnit.cpp -O2 $cxxflags -o bug-O2 && ./bug-O2 Illegal instruction (core dumped) $ g++ -std=c++14 DwarfCompileUnit.cpp -O1 $cxxflags -o bug-O1 && ./bug-O1 <ok> It's a very fragile test: - any inlines I try seem to repair the test - -fno-strict-aliasing unbreaks it (I believe the code is strict-aliasing clean) - optimization option changes repair the test $ g++ -v Using built-in specs. COLLECT_GCC=/<<NIX>>/gcc-14.0.0/bin/g++ COLLECT_LTO_WRAPPER=/<<NIX>>/gcc-14.0.0/libexec/gcc/x86_64-unknown-linux-gnu/14.0.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: Thread model: posix Supported LTO compression algorithms: zlib gcc version 14.0.0 99999999 (experimental) (GCC)
next reply other threads:[~2023-07-01 21:52 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-01 21:52 slyfox at gcc dot gnu.org [this message] 2023-07-01 21:56 ` [Bug middle-end/110515] " slyfox at gcc dot gnu.org 2023-07-01 22:11 ` pinskia at gcc dot gnu.org 2023-07-01 22:12 ` [Bug middle-end/110515] " pinskia at gcc dot gnu.org 2023-07-01 22:12 ` [Bug middle-end/110515] [12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-07-01 22:37 ` pinskia at gcc dot gnu.org 2023-07-01 23:32 ` pinskia at gcc dot gnu.org 2023-07-03 7:12 ` rguenth at gcc dot gnu.org 2023-07-04 22:40 ` slyfox at gcc dot gnu.org 2023-07-05 10:57 ` rguenth at gcc dot gnu.org 2023-07-05 12:36 ` rguenth at gcc dot gnu.org 2023-07-05 13:55 ` rguenth at gcc dot gnu.org 2023-07-06 7:30 ` cvs-commit at gcc dot gnu.org 2023-07-06 7:30 ` [Bug middle-end/110515] [12/13 " rguenth at gcc dot gnu.org 2023-07-06 10:09 ` slyfox at gcc dot gnu.org 2023-07-07 12:07 ` [Bug middle-end/110515] [12 " cvs-commit at gcc dot gnu.org 2023-11-27 11:34 ` cvs-commit at gcc dot gnu.org 2023-11-27 11:38 ` rguenth 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-110515-4@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).