From: Jeff Law <law@redhat.com>
To: gcc-patches@gcc.gnu.org, richard.sandiford@arm.com
Subject: Re: [5/9] Remove IOR_HARD_REG_SET
Date: Mon, 09 Sep 2019 17:39:00 -0000 [thread overview]
Message-ID: <2c7c1ff4-acb4-ef01-8f64-bc0e35c31c5e@redhat.com> (raw)
In-Reply-To: <mpt8sqx8nol.fsf@arm.com>
On 9/9/19 10:00 AM, Richard Sandiford wrote:
> Use "x |= y" instead of "IOR_HARD_REG_SET (x, y)" (or just "x | y"
> if the result is a temporary).
>
>
> 2019-09-09 Richard Sandiford <richard.sandiford@arm.com>
>
> gcc/
> * hard-reg-set.h (HARD_REG_SET::operator|): New function.
> (HARD_REG_SET::operator|=): Likewise.
> (IOR_HARD_REG_SET): Delete.
> * config/gcn/gcn.c (gcn_md_reorg): Use "|" instead of
> IOR_HARD_REG_SET.
> * config/m32c/m32c.c (m32c_register_move_cost): Likewise.
> * config/s390/s390.c (s390_adjust_loop_scan_osc): Likewise.
> * final.c (collect_fn_hard_reg_usage): Likewise.
> * hw-doloop.c (scan_loop, optimize_loop): Likewise.
> * ira-build.c (merge_hard_reg_conflicts): Likewise.
> (ior_hard_reg_conflicts, create_cap_allocno, propagate_allocno_info)
> (propagate_some_info_from_allocno): Likewise.
> (copy_info_to_removed_store_destinations): Likewise.
> * ira-color.c (add_allocno_hard_regs_to_forest, assign_hard_reg)
> (allocno_reload_assign, ira_reassign_pseudos): Likewise.
> (fast_allocation): Likewise.
> * ira-conflicts.c (ira_build_conflicts): Likewise.
> * ira-lives.c (make_object_dead, process_single_reg_class_operands)
> (process_bb_node_lives): Likewise.
> * ira.c (setup_pressure_classes, setup_reg_class_relations): Likewise.
> * lra-assigns.c (find_hard_regno_for_1): Likewise.
> (setup_live_pseudos_and_spill_after_risky_transforms): Likewise.
> * lra-constraints.c (process_alt_operands, inherit_in_ebb): Likewise.
> * lra-eliminations.c (spill_pseudos, update_reg_eliminate): Likewise.
> * lra-lives.c (mark_pseudo_dead, check_pseudos_live_through_calls)
> (process_bb_lives): Likewise.
> * lra-spills.c (assign_spill_hard_regs): Likewise.
> * postreload.c (reload_combine): Likewise.
> * reginfo.c (init_reg_sets_1): Likewise.
> * regrename.c (merge_overlapping_regs, find_rename_reg)
> (merge_chains): Likewise.
> * reload1.c (maybe_fix_stack_asms, order_regs_for_reload, find_reg)
> (find_reload_regs, finish_spills, choose_reload_regs_init)
> (emit_reload_insns): Likewise.
> * reorg.c (redundant_insn): Likewise.
> * resource.c (find_dead_or_set_registers, mark_set_resources)
> (mark_target_live_regs): Likewise.
> * rtlanal.c (find_all_hard_reg_sets): Likewise.
> * sched-deps.c (sched_analyze_insn): Likewise.
> * sel-sched.c (mark_unavailable_hard_regs): Likewise.
> (find_best_reg_for_expr): Likewise.
> * shrink-wrap.c (try_shrink_wrapping): Likewise.
>
OK
jeff
next prev parent reply other threads:[~2019-09-09 17:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 15:52 [0/9] Make HARD_REG_SETs easier to use Richard Sandiford
2019-09-09 15:54 ` [1/9] Simplify the implementation of HARD_REG_SET Richard Sandiford
2019-09-09 17:35 ` Jeff Law
2019-09-09 18:05 ` Richard Sandiford
2019-09-10 9:16 ` Oleg Endo
2019-09-09 15:58 ` [2/9] Remove COPY_HARD_REG_SET Richard Sandiford
2019-09-09 17:36 ` Jeff Law
2019-09-09 15:59 ` [3/9] Remove COMPL_HARD_REG_SET Richard Sandiford
2019-09-09 17:37 ` Jeff Law
2019-09-09 16:00 ` [4/9] Remove AND_HARD_REG_SET Richard Sandiford
2019-09-09 17:38 ` Jeff Law
2019-09-09 16:00 ` [5/9] Remove IOR_HARD_REG_SET Richard Sandiford
2019-09-09 17:39 ` Jeff Law [this message]
2019-09-09 16:01 ` [7/9] Remove IOR_COMPL_HARD_REG_SET Richard Sandiford
2019-09-09 17:41 ` Jeff Law
2019-09-09 16:01 ` [6/9] Remove AND_COMPL_HARD_REG_SET Richard Sandiford
2019-09-09 17:40 ` Jeff Law
2019-09-09 16:02 ` [8/9] Remove hard_reg_set_equal_p Richard Sandiford
2019-09-09 17:41 ` Jeff Law
2019-09-09 16:03 ` [9/9] Tweak interface to ira-build.c:ior_hard_reg_conflicts Richard Sandiford
2019-09-09 17:42 ` Jeff Law
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=2c7c1ff4-acb4-ef01-8f64-bc0e35c31c5e@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).