public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/107769] [12/13 Regression] -flto with -Os/-O2/-O3 emitted code with gcc 12.x segfaults via mutated global in .rodata since r12-2887-ga6da2cddcf0e959d Date: Thu, 06 Apr 2023 17:01:15 +0000 [thread overview] Message-ID: <bug-107769-4-IrFbZlouoH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107769-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107769 --- Comment #7 from Martin Jambor <jamborm at gcc dot gnu.org> --- Created attachment 54817 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54817&action=edit potential patch I am testing the attached patch. I'd like to think about the whole situation a bit more next week, but this seems like a way to fix this and PR 109318.
next prev parent reply other threads:[~2023-04-06 17:01 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-20 15:54 [Bug c/107769] New: -flto with -Os/-O2/-O3 emitted code with gcc 12.x segfaults via mutated global in .rodata resence at parsoma dot net 2022-11-20 18:23 ` [Bug ipa/107769] [12/13 Regression] " pinskia at gcc dot gnu.org 2022-11-21 8:45 ` [Bug ipa/107769] [12/13 Regression] -flto with -Os/-O2/-O3 emitted code with gcc 12.x segfaults via mutated global in .rodata since r12-2887-ga6da2cddcf0e959d marxin at gcc dot gnu.org 2022-11-21 10:29 ` hubicka at gcc dot gnu.org 2022-11-22 8:33 ` rguenth at gcc dot gnu.org 2023-03-24 13:51 ` jamborm at gcc dot gnu.org 2023-03-30 3:35 ` yinyuefengyi at gmail dot com 2023-03-31 11:09 ` jamborm at gcc dot gnu.org 2023-04-06 17:01 ` jamborm at gcc dot gnu.org [this message] 2023-04-17 11:06 ` cvs-commit at gcc dot gnu.org 2023-04-17 14:17 ` [Bug ipa/107769] [12 " jamborm at gcc dot gnu.org 2023-04-26 16:45 ` cvs-commit at gcc dot gnu.org 2023-04-26 16:46 ` jamborm 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-107769-4-IrFbZlouoH@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).