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 middle-end/104971] [9/10/11 Regression] Optimisation for __builtin_ia32_readeflags corrupts the stack Date: Fri, 25 Mar 2022 16:31:05 +0000 [thread overview] Message-ID: <bug-104971-4-xoNLK0LFuc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104971-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104971 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Vladimir Makarov <vmakarov@gcc.gnu.org>: https://gcc.gnu.org/g:25725506b85f478076770942d76799c54310c696 commit r12-7817-g25725506b85f478076770942d76799c54310c696 Author: Vladimir N. Makarov <vmakarov@redhat.com> Date: Fri Mar 25 12:22:08 2022 -0400 [PR104971] LRA: check live hard regs to remove a dead insn LRA removes insn modifying sp for given PR test set. We should also have checked living hard regs to prevent this. The patch fixes this. gcc/ChangeLog: PR middle-end/104971 * lra-lives.cc (process_bb_lives): Check hard_regs_live for hard regs to clear remove_p flag.
next prev parent reply other threads:[~2022-03-25 16:31 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-17 18:49 [Bug middle-end/104971] New: " andrew.cooper3 at citrix dot com 2022-03-17 19:05 ` [Bug middle-end/104971] [9/10/11/12 Regression] " jakub at gcc dot gnu.org 2022-03-17 19:35 ` jakub at gcc dot gnu.org 2022-03-17 20:49 ` andrew.cooper3 at citrix dot com 2022-03-17 21:12 ` mpolacek at gcc dot gnu.org 2022-03-18 17:32 ` jakub at gcc dot gnu.org 2022-03-19 12:53 ` cvs-commit at gcc dot gnu.org 2022-03-25 16:31 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-29 5:54 ` [Bug middle-end/104971] [9/10/11 " cvs-commit at gcc dot gnu.org 2022-03-30 8:17 ` [Bug middle-end/104971] [9/10 " jakub at gcc dot gnu.org 2022-05-10 8:25 ` cvs-commit at gcc dot gnu.org 2022-05-11 6:25 ` 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-104971-4-xoNLK0LFuc@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).