public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jose E. Marchesi <jemarch@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-2455] bpf: remove unused variables from bpf_expand_{prologue, epilogue} Date: Tue, 6 Sep 2022 07:00:28 +0000 (GMT) [thread overview] Message-ID: <20220906070028.58FBF385AC19@sourceware.org> (raw) https://gcc.gnu.org/g:2a2fb3e30c2f80b978d83e01346665f139ffeebb commit r13-2455-g2a2fb3e30c2f80b978d83e01346665f139ffeebb Author: Jose E. Marchesi <jose.marchesi@oracle.com> Date: Tue Sep 6 08:58:23 2022 +0200 bpf: remove unused variables from bpf_expand_{prologue,epilogue} gcc/ChangeLog: * config/bpf/bpf.cc (bpf_expand_prologue): Remove unused automatic `insn'. (bpf_expand_epilogue): Likewise. Diff: --- gcc/config/bpf/bpf.cc | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/gcc/config/bpf/bpf.cc b/gcc/config/bpf/bpf.cc index 9cb56cfb287..51055651707 100644 --- a/gcc/config/bpf/bpf.cc +++ b/gcc/config/bpf/bpf.cc @@ -428,7 +428,6 @@ bpf_compute_frame_layout (void) void bpf_expand_prologue (void) { - rtx insn; HOST_WIDE_INT size; size = (cfun->machine->local_vars_size @@ -468,7 +467,7 @@ bpf_expand_prologue (void) plus_constant (DImode, hard_frame_pointer_rtx, fp_offset - 8)); - insn = emit_move_insn (mem, gen_rtx_REG (DImode, regno)); + emit_move_insn (mem, gen_rtx_REG (DImode, regno)); fp_offset -= 8; } } @@ -481,15 +480,15 @@ bpf_expand_prologue (void) accessor. */ if (cfun->calls_alloca) { - insn = emit_move_insn (stack_pointer_rtx, - hard_frame_pointer_rtx); + emit_move_insn (stack_pointer_rtx, + hard_frame_pointer_rtx); if (size > 0) { - insn = emit_insn (gen_rtx_SET (stack_pointer_rtx, - gen_rtx_PLUS (Pmode, - stack_pointer_rtx, - GEN_INT (-size)))); + emit_insn (gen_rtx_SET (stack_pointer_rtx, + gen_rtx_PLUS (Pmode, + stack_pointer_rtx, + GEN_INT (-size)))); } } } @@ -504,7 +503,6 @@ bpf_expand_epilogue (void) not restoring callee-saved registers in BPF. */ if (TARGET_XBPF) { - rtx insn; int regno; int fp_offset = -cfun->machine->local_vars_size; @@ -528,7 +526,7 @@ bpf_expand_epilogue (void) plus_constant (DImode, hard_frame_pointer_rtx, fp_offset - 8)); - insn = emit_move_insn (gen_rtx_REG (DImode, regno), mem); + emit_move_insn (gen_rtx_REG (DImode, regno), mem); fp_offset -= 8; } }
reply other threads:[~2022-09-06 7:00 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220906070028.58FBF385AC19@sourceware.org \ --to=jemarch@gcc.gnu.org \ --cc=gcc-cvs@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).