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/82735] _mm256_zeroupper does not invalidate previously computed registers Date: Mon, 07 Jun 2021 02:25:27 +0000 [thread overview] Message-ID: <bug-82735-4-HKq28yKQLO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-82735-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82735 --- Comment #17 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by hongtao Liu <liuhongt@gcc.gnu.org>: https://gcc.gnu.org/g:16465ceb06cc1f65cfca3c0eb2c1ee27ab03bdfd commit r12-1252-g16465ceb06cc1f65cfca3c0eb2c1ee27ab03bdfd Author: liuhongt <hongtao.liu@intel.com> Date: Tue Jun 1 09:00:57 2021 +0800 CALL_INSN may not be a real function call. Use "used" flag for CALL_INSN to indicate it's a fake call. If it's a fake call, it won't have its own function stack. gcc/ChangeLog PR target/82735 * df-scan.c (df_get_call_refs): When call_insn is a fake call, it won't use stack pointer reg. * final.c (leaf_function_p): When call_insn is a fake call, it won't affect caller as a leaf function. * reg-stack.c (callee_clobbers_any_stack_reg): New. (subst_stack_regs): When call_insn doesn't clobber any stack reg, don't clear the arguments. * rtl.c (shallow_copy_rtx): Don't clear flag used when orig is a insn. * shrink-wrap.c (requires_stack_frame_p): No need for stack frame for a fake call. * rtl.h (FAKE_CALL_P): New macro.
next prev parent reply other threads:[~2021-06-07 2:25 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-82735-4@http.gcc.gnu.org/bugzilla/> 2021-04-24 14:17 ` noloader at gmail dot com 2021-04-24 14:36 ` noloader at gmail dot com 2021-04-25 8:28 ` crazylht at gmail dot com 2021-04-28 9:07 ` ubizjak at gmail dot com 2021-04-28 9:13 ` ubizjak at gmail dot com 2021-04-28 9:19 ` jakub at gcc dot gnu.org 2021-04-28 9:46 ` ubizjak at gmail dot com 2021-04-28 11:08 ` crazylht at gmail dot com 2021-04-28 13:02 ` marcin.slusarz at intel dot com 2021-04-29 5:56 ` crazylht at gmail dot com 2021-05-06 7:43 ` crazylht at gmail dot com 2021-05-07 3:22 ` crazylht at gmail dot com 2021-06-07 2:25 ` cvs-commit at gcc dot gnu.org [this message] 2021-06-07 2:25 ` cvs-commit at gcc dot gnu.org 2021-06-07 2:26 ` crazylht at gmail dot com 2021-06-07 19:06 ` cvs-commit at gcc dot gnu.org 2023-06-27 6:13 ` 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-82735-4-HKq28yKQLO@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).