From: Jeff Law <law@redhat.com>
To: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: [11/32] Remove global call sets: cse.c
Date: Sun, 29 Sep 2019 21:04:00 -0000 [thread overview]
Message-ID: <66f112a0-6bd8-6c2a-4c85-41c90641964c@redhat.com> (raw)
In-Reply-To: <mptsgokid2r.fsf@arm.com>
On 9/25/19 9:57 AM, Richard Sandiford wrote:
> Richard Sandiford <richard.sandiford@arm.com> writes:
>> Like with the combine.c patch, this one keeps things simple by
>> invalidating values in partially-clobbered registers, rather than
>> trying to tell whether the value in a partially-clobbered register
>> is actually clobbered or not. Again, this is in principle a bug fix,
>> but probably never matters in practice.
>
> Similary to the combine patch, I've updated this to avoid the
> short "abi" name and use a temporary HARD_REG_SET instead.
>
> Richard
>
>
> 2019-09-25 Richard Sandiford <richard.sandiford@arm.com>
>
> gcc/
> * cse.c: Include regs.h and function-abi.h.
> (invalidate_for_call): Take the call insn as an argument.
> Use insn_callee_abi to get the ABI of the call and invalidate
> partially clobbered registers as well as fully clobbered ones.
> (cse_insn): Update call accordingly.
>
> Index: gcc/cse.c
> ===================================================================
> --- gcc/cse.c 2019-09-17 15:27:11.338066929 +0100
> +++ gcc/cse.c 2019-09-25 16:55:31.202641509 +0100
> @@ -42,6 +42,8 @@ Software Foundation; either version 3, o
> #include "tree-pass.h"
> #include "dbgcnt.h"
> #include "rtl-iter.h"
> +#include "regs.h"
> +#include "function-abi.h"
>
> /* The basic idea of common subexpression elimination is to go
> through the code, keeping a record of expressions that would
> @@ -566,7 +568,6 @@ static void remove_invalid_subreg_refs (
> machine_mode);
> static void rehash_using_reg (rtx);
> static void invalidate_memory (void);
> -static void invalidate_for_call (void);
> static rtx use_related_value (rtx, struct table_elt *);
>
> static inline unsigned canon_hash (rtx, machine_mode);
> @@ -2091,23 +2092,29 @@ rehash_using_reg (rtx x)
> }
> \f
> /* Remove from the hash table any expression that is a call-clobbered
> - register. Also update their TICK values. */
> + register in INSN. Also update their TICK values. */
>
> static void
> -invalidate_for_call (void)
> +invalidate_for_call (rtx_insn *insn)
> {
> - unsigned int regno, endregno;
> - unsigned int i;
> + unsigned int regno;
> unsigned hash;
> struct table_elt *p, *next;
> int in_table = 0;
> hard_reg_set_iterator hrsi;
>
> - /* Go through all the hard registers. For each that is clobbered in
> - a CALL_INSN, remove the register from quantity chains and update
> + /* Go through all the hard registers. For each that might be clobbered
> + in call insn INSN, remove the register from quantity chains and update
> reg_tick if defined. Also see if any of these registers is currently
> - in the table. */
> - EXECUTE_IF_SET_IN_HARD_REG_SET (regs_invalidated_by_call, 0, regno, hrsi)
> + in the table.
> +
> + ??? We could be more precise for partially-clobbered registers,
> + and only invalidate values that actually occupy the clobbered part
> + of the registers. It doesn't seem worth the effort though, since
> + we shouldn't see this situation much before RA. */
> + HARD_REG_SET callee_clobbers
> + = insn_callee_abi (insn).full_and_partial_reg_clobbers ();
> + EXECUTE_IF_SET_IN_HARD_REG_SET (callee_clobbers, 0, regno, hrsi)
> {
> delete_reg_equiv (regno);
> if (REG_TICK (regno) >= 0)
> @@ -2132,15 +2139,11 @@ invalidate_for_call (void)
> || REGNO (p->exp) >= FIRST_PSEUDO_REGISTER)
> continue;
>
> - regno = REGNO (p->exp);
> - endregno = END_REGNO (p->exp);
> -
> - for (i = regno; i < endregno; i++)
> - if (TEST_HARD_REG_BIT (regs_invalidated_by_call, i))
> - {
> - remove_from_table (p, hash);
> - break;
> - }
> + /* This must use the same test as above rather than the
> + more accurate clobbers_reg_p. */
> + if (overlaps_hard_reg_set_p (callee_clobbers, GET_MODE (p->exp),
> + REGNO (p->exp)))
Is it worth putting a forward comment to the earlier test to the later
one to help ensure they're kept in sync?
OK with or without that comment update.
next prev parent reply other threads:[~2019-09-29 21:04 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 19:02 [00/32] Support multiple ABIs in the same translation unit Richard Sandiford
2019-09-11 19:03 ` [02/32] Add a target hook for getting an ABI from a function type Richard Sandiford
2019-09-29 20:52 ` Jeff Law
2019-09-11 19:03 ` [01/32] Add function_abi.{h,cc} Richard Sandiford
2019-09-29 20:51 ` Jeff Law
2019-09-30 9:19 ` Richard Sandiford
2019-09-30 21:16 ` Jeff Law
2019-09-11 19:04 ` [03/32] Add a function for getting the ABI of a call insn target Richard Sandiford
2019-09-25 15:38 ` Richard Sandiford
2019-09-30 15:52 ` Jeff Law
2019-09-30 16:32 ` Richard Sandiford
2019-09-30 16:46 ` Jeff Law
2019-09-11 19:05 ` [04/32] [x86] Robustify vzeroupper handling across calls Richard Sandiford
2019-09-25 15:48 ` Richard Sandiford
2019-09-25 18:11 ` Uros Bizjak
2019-10-01 10:14 ` Uros Bizjak
2019-10-08 18:17 ` Uros Bizjak
2019-09-11 19:05 ` [05/32] Pass an ABI identifier to hard_regno_call_part_clobbered Richard Sandiford
2019-09-29 20:58 ` Jeff Law
2019-09-11 19:06 ` [06/32] Pass an ABI to choose_hard_reg_mode Richard Sandiford
2019-09-29 21:00 ` Jeff Law
2019-09-11 19:07 ` [08/32] Remove global call sets: cfgcleanup.c Richard Sandiford
2019-09-29 21:02 ` Jeff Law
2019-09-11 19:07 ` [07/32] Remove global call sets: caller-save.c Richard Sandiford
2019-09-29 21:01 ` Jeff Law
2019-09-11 19:08 ` [10/32] Remove global call sets: combine.c Richard Sandiford
2019-09-12 2:18 ` Segher Boessenkool
2019-09-12 7:52 ` Richard Sandiford
2019-09-20 0:43 ` Segher Boessenkool
2019-09-25 15:52 ` Richard Sandiford
2019-09-25 16:30 ` Segher Boessenkool
2019-09-29 22:32 ` Jeff Law
2019-09-29 22:43 ` Segher Boessenkool
2019-09-11 19:08 ` [09/32] Remove global call sets: cfgloopanal.c Richard Sandiford
2019-09-29 21:02 ` Jeff Law
2019-09-11 19:09 ` [11/32] Remove global call sets: cse.c Richard Sandiford
2019-09-25 15:57 ` Richard Sandiford
2019-09-29 21:04 ` Jeff Law [this message]
2019-09-30 16:23 ` Richard Sandiford
2019-09-11 19:09 ` [12/32] Remove global call sets: cselib.c Richard Sandiford
2019-09-29 21:05 ` Jeff Law
2019-10-29 9:20 ` Martin Liška
2019-09-11 19:10 ` [14/32] Remove global call sets: DF (entry/exit defs) Richard Sandiford
2019-09-29 21:07 ` Jeff Law
2019-09-11 19:10 ` [13/32] Remove global call sets: DF (EH edges) Richard Sandiford
2019-09-29 21:07 ` Jeff Law
2019-09-11 19:11 ` [16/32] Remove global call sets: function.c Richard Sandiford
2019-09-29 21:10 ` Jeff Law
2019-09-11 19:11 ` [15/32] Remove global call sets: early-remat.c Richard Sandiford
2019-09-29 21:09 ` Jeff Law
2019-09-11 19:11 ` [17/32] Remove global call sets: gcse.c Richard Sandiford
2019-09-25 16:04 ` Richard Sandiford
2019-09-29 21:10 ` Jeff Law
2019-09-11 19:12 ` [19/32] Remove global call sets: IRA Richard Sandiford
2019-09-30 15:16 ` Jeff Law
2019-09-11 19:12 ` [18/32] Remove global call sets: haifa-sched.c Richard Sandiford
2019-09-29 21:11 ` Jeff Law
2019-09-11 19:13 ` [20/32] Remove global call sets: loop-iv.c Richard Sandiford
2019-09-29 21:20 ` Jeff Law
2019-09-11 19:14 ` [21/32] Remove global call sets: LRA Richard Sandiford
2019-09-30 15:29 ` Jeff Law
2019-10-04 18:03 ` H.J. Lu
2019-10-04 21:52 ` H.J. Lu
2019-10-05 13:33 ` Richard Sandiford
2019-09-11 19:14 ` [22/32] Remove global call sets: postreload.c Richard Sandiford
2019-09-29 21:33 ` Jeff Law
2019-09-11 19:14 ` [23/32] Remove global call sets: postreload-gcse.c Richard Sandiford
2019-09-25 16:08 ` Richard Sandiford
2019-09-29 22:22 ` Jeff Law
2019-09-11 19:15 ` [25/32] Remove global call sets: regcprop.c Richard Sandiford
2019-09-29 21:34 ` Jeff Law
2019-09-11 19:15 ` [24/32] Remove global call sets: recog.c Richard Sandiford
2019-09-29 21:33 ` Jeff Law
2019-09-11 19:16 ` [27/32] Remove global call sets: reload.c Richard Sandiford
2019-09-29 22:26 ` Jeff Law
2019-09-11 19:16 ` [26/32] Remove global call sets: regrename.c Richard Sandiford
2019-09-29 22:25 ` Jeff Law
2019-09-11 19:17 ` [29/32] Remove global call sets: sched-deps.c Richard Sandiford
2019-09-29 22:20 ` Jeff Law
2019-10-04 14:32 ` Christophe Lyon
2019-10-04 14:35 ` Richard Sandiford
2019-10-04 14:37 ` Christophe Lyon
2019-10-07 13:29 ` Christophe Lyon
2019-09-11 19:17 ` [00/32] Remove global call sets: rtlanal.c Richard Sandiford
2019-09-29 22:21 ` Jeff Law
2019-09-11 19:18 ` [31/32] Remove global call sets: shrink-wrap.c Richard Sandiford
2019-09-29 22:21 ` Jeff Law
2019-09-11 19:18 ` [30/32] Remove global call sets: sel-sched.c Richard Sandiford
2019-09-30 15:08 ` Jeff Law
2019-09-11 19:19 ` [32/32] Hide regs_invalidated_by_call etc Richard Sandiford
2019-09-29 22:22 ` Jeff Law
2019-09-12 20:42 ` [00/32] Support multiple ABIs in the same translation unit Steven Bosscher
2019-09-26 19:24 ` Dimitar Dimitrov
2019-09-27 8:58 ` Richard Sandiford
2019-10-01 2:09 ` build-failure for cris-elf with "[00/32] Support multiple ABIs in the same translation unit" Hans-Peter Nilsson
2019-10-01 7:51 ` Richard Sandiford
2019-10-01 10:58 ` Hans-Peter Nilsson
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=66f112a0-6bd8-6c2a-4c85-41c90641964c@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.sandiford@arm.com \
/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: link
Be 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).