public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tedheadster at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486 Date: Fri, 15 Jan 2021 13:26:51 +0000 [thread overview] Message-ID: <bug-98667-4-2jNPxb57w9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98667-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 --- Comment #11 from Matthew Whitehead <tedheadster at gmail dot com> --- A patch has been proposed to remove the -fcf-protection=full from the ebuild script: https://bugs.gentoo.org/765442
next prev parent reply other threads:[~2021-01-15 13:26 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-14 1:24 [Bug c++/98667] New: " tedheadster at gmail dot com 2021-01-14 1:28 ` [Bug c++/98667] " tedheadster at gmail dot com 2021-01-14 7:28 ` [Bug target/98667] " pinskia at gcc dot gnu.org 2021-01-14 11:53 ` tedheadster at gmail dot com 2021-01-14 13:22 ` tedheadster at gmail dot com 2021-01-14 13:29 ` jakub at gcc dot gnu.org 2021-01-14 14:04 ` rguenth at gcc dot gnu.org 2021-01-14 14:07 ` hjl.tools at gmail dot com 2021-01-14 14:08 ` hjl.tools at gmail dot com 2021-01-14 15:43 ` cvs-commit at gcc dot gnu.org 2021-01-14 15:45 ` hjl.tools at gmail dot com 2021-01-15 13:26 ` tedheadster at gmail dot com [this message] 2021-04-27 13:12 ` hjl.tools at gmail dot com 2021-07-15 17:40 ` hjl.tools at gmail dot com 2021-10-21 15:22 ` marxin at gcc dot gnu.org 2021-10-21 15:55 ` hjl.tools at gmail dot com 2021-10-21 16:14 ` marxin at gcc dot gnu.org 2021-10-21 19:09 ` cvs-commit at gcc dot gnu.org 2021-10-21 19:10 ` cvs-commit at gcc dot gnu.org 2021-10-21 19:11 ` cvs-commit at gcc dot gnu.org 2021-10-21 19:14 ` cvs-commit 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-98667-4-2jNPxb57w9@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).