public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/93492] Broken code with -fpatchable-function-entry and -fcf-protection=full Date: Sun, 12 Jul 2020 12:07:34 +0000 [thread overview] Message-ID: <bug-93492-4-N4HwwAyabj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93492-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93492 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution|--- |FIXED --- Comment #36 from H.J. Lu <hjl.tools at gmail dot com> --- Fixed for GCC 11.
prev parent reply other threads:[~2020-07-12 12:07 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93492-4@http.gcc.gnu.org/bugzilla/> 2020-05-02 4:07 ` cvs-commit at gcc dot gnu.org 2020-05-07 11:56 ` jakub at gcc dot gnu.org 2020-06-12 3:45 ` cvs-commit at gcc dot gnu.org 2020-06-12 3:49 ` hjl.tools at gmail dot com 2020-06-14 15:38 ` ro at gcc dot gnu.org 2020-06-14 15:47 ` hjl.tools at gmail dot com 2020-06-14 16:52 ` iains at gcc dot gnu.org 2020-06-15 13:12 ` hjl.tools at gmail dot com 2020-06-26 23:13 ` hjl.tools at gmail dot com 2020-07-10 12:57 ` ro at CeBiTec dot Uni-Bielefeld.DE 2020-07-10 13:56 ` hjl.tools at gmail dot com 2020-07-10 14:03 ` ro at CeBiTec dot Uni-Bielefeld.DE 2020-07-10 14:04 ` hjl.tools at gmail dot com 2020-07-10 14:06 ` ro at CeBiTec dot Uni-Bielefeld.DE 2020-07-10 14:12 ` hjl.tools at gmail dot com 2020-07-10 14:16 ` ro at CeBiTec dot Uni-Bielefeld.DE 2020-07-10 14:33 ` hjl.tools at gmail dot com 2020-07-10 14:41 ` ro at CeBiTec dot Uni-Bielefeld.DE 2020-07-10 15:53 ` mikestump at comcast dot net 2020-07-10 21:54 ` hjl.tools at gmail dot com 2020-07-12 12:06 ` cvs-commit at gcc dot gnu.org 2020-07-12 12:07 ` hjl.tools at gmail dot com [this message]
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-93492-4-N4HwwAyabj@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).