public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115038] [14/15 regression] internal error in seh_cfa_offset with -O2 -fno-omit-frame-pointer Date: Sun, 12 May 2024 16:00:17 +0000 [thread overview] Message-ID: <bug-115038-4-TbshsPvtgO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115038-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115038 --- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- It's the -ffold-mem-offsets pass messing up with the prologue and the frame-related instructions (so -fno-fold-mem-offsets is a workaround).
next prev parent reply other threads:[~2024-05-12 16:00 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-10 15:44 [Bug c++/115038] New: ICE in seh_cfa_offset since 14.1.0 reiter.christoph at gmail dot com 2024-05-11 12:15 ` [Bug target/115038] " reiter.christoph at gmail dot com 2024-05-12 15:42 ` [Bug target/115038] [14/15 regression] internal error in seh_cfa_offset with -O2 -fno-omit-frame-pointer ebotcazou at gcc dot gnu.org 2024-05-12 16:00 ` ebotcazou at gcc dot gnu.org [this message] 2024-05-12 16:33 ` ebotcazou at gcc dot gnu.org 2024-05-12 18:15 ` reiter.christoph at gmail dot com 2024-05-13 5:45 ` reiter.christoph at gmail dot com 2024-05-13 9:35 ` rguenth at gcc dot gnu.org 2024-05-20 6:25 ` [Bug rtl-optimization/115038] " ebotcazou at gcc dot gnu.org 2024-05-20 7:12 ` ebotcazou at gcc dot gnu.org 2024-05-22 14:48 ` law at gcc dot gnu.org 2024-05-22 16:04 ` ebotcazou at gcc dot gnu.org 2024-05-22 16:14 ` cvs-commit at gcc dot gnu.org 2024-05-22 18:54 ` cvs-commit at gcc dot gnu.org 2024-05-22 18:55 ` ebotcazou 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-115038-4-TbshsPvtgO@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).