public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "luke-jr+gccbugs at utopios dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/102993] -fcf-protection=full produces segfaulting code when targeting 32-bit x86 (i686) Date: Fri, 29 Oct 2021 17:41:34 +0000 [thread overview] Message-ID: <bug-102993-4-zYoKxEIMEQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102993-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102993 --- Comment #7 from Luke Dashjr <luke-jr+gccbugs at utopios dot org> --- It's the standard Ubuntu focal g++-mingw-w64-i686 package.
next prev parent reply other threads:[~2021-10-29 17:41 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-28 23:56 [Bug other/102993] New: -mcf-protection=full " luke-jr+gccbugs at utopios dot org 2021-10-29 0:09 ` [Bug target/102993] -fcf-protection=full " pinskia at gcc dot gnu.org 2021-10-29 0:33 ` luke-jr+gccbugs at utopios dot org 2021-10-29 6:53 ` rguenth at gcc dot gnu.org 2021-10-29 7:05 ` ebotcazou at gcc dot gnu.org 2021-10-29 8:04 ` rguenth at gcc dot gnu.org 2021-10-29 8:08 ` ebotcazou at gcc dot gnu.org 2021-10-29 17:41 ` luke-jr+gccbugs at utopios dot org [this message] 2021-10-30 17:14 ` ebotcazou at gcc dot gnu.org 2022-12-27 7:11 ` nightstrike at gmail dot com
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-102993-4-zYoKxEIMEQ@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).