public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/103925] Missing int3 in ix86_output_indirect_function_return Date: Thu, 06 Jan 2022 19:53:58 +0000 [thread overview] Message-ID: <bug-103925-4-YNNkkOoghC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103925-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103925 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>: https://gcc.gnu.org/g:c2e5c4feed32c808591b5278f680bbabe63eb225 commit r12-6321-gc2e5c4feed32c808591b5278f680bbabe63eb225 Author: H.J. Lu <hjl.tools@gmail.com> Date: Wed Jan 5 18:04:21 2022 -0800 x86: Generate INT3 for __builtin_eh_return Generate INT3 after indirect jmp in exception return for -fcf-protection with -mharden-sls=indirect-jmp. gcc/ PR target/103925 * config/i386/i386.c (ix86_output_indirect_function_return): Generate INT3 after indirect jmp for -mharden-sls=indirect-jmp. gcc/testsuite/ PR target/103925 * gcc.target/i386/harden-sls-6.c: New test.
next prev parent reply other threads:[~2022-01-06 19:53 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-06 2:03 [Bug target/103925] New: " hjl.tools at gmail dot com 2022-01-06 2:47 ` [Bug target/103925] " pinskia at gcc dot gnu.org 2022-01-06 2:54 ` hjl.tools at gmail dot com 2022-01-06 2:56 ` pinskia at gcc dot gnu.org 2022-01-06 19:53 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-06 20:12 ` hjl.tools at gmail dot com 2022-02-16 14:01 ` 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-103925-4-YNNkkOoghC@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).