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/96536] -fcf-protection code in i386.md:restore_stack_nonlocal uses invalid compare-and-jump rtl Date: Tue, 18 Aug 2020 17:49:57 +0000 [thread overview] Message-ID: <bug-96536-4-NG8Gz4l4g4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96536-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96536 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-8 branch has been updated by Uros Bizjak <uros@gcc.gnu.org>: https://gcc.gnu.org/g:bf7b9330982165e051de0962c5bc231e2d1242d9 commit r8-10410-gbf7b9330982165e051de0962c5bc231e2d1242d9 Author: Uros Bizjak <ubizjak@gmail.com> Date: Tue Aug 18 19:48:51 2020 +0200 i386: Fix restore_stack_nonlocal expander [PR96536]. -fcf-protection code in restore_stack_nonlocal uses a branch based on a clobber result. The patch adds missing compare. 2020-08-18 Uroš Bizjak <ubizjak@gmail.com> gcc/ChangeLog: PR target/96536 * config/i386/i386.md (restore_stack_nonlocal): Add missing compare RTX.
next prev parent reply other threads:[~2020-08-18 17:49 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-08 10:36 [Bug target/96536] New: " rsandifo at gcc dot gnu.org 2020-08-10 8:43 ` [Bug target/96536] " crazylht at gmail dot com 2020-08-10 9:04 ` ubizjak at gmail dot com 2020-08-10 9:32 ` crazylht at gmail dot com 2020-08-13 21:06 ` ubizjak at gmail dot com 2020-08-14 6:33 ` crazylht at gmail dot com 2020-08-17 14:39 ` ubizjak at gmail dot com 2020-08-18 8:54 ` crazylht at gmail dot com 2020-08-18 15:32 ` cvs-commit at gcc dot gnu.org 2020-08-18 15:36 ` cvs-commit at gcc dot gnu.org 2020-08-18 16:49 ` cvs-commit at gcc dot gnu.org 2020-08-18 17:49 ` cvs-commit at gcc dot gnu.org [this message] 2020-08-18 17:50 ` ubizjak 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-96536-4-NG8Gz4l4g4@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).