From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Richard Biener <richard.guenther@gmail.com>,
Andrea Corallo <andrea.corallo@arm.com>
Cc: nd <nd@arm.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/2] Add new RTX instruction class FILLER_INSN
Date: Wed, 22 Jul 2020 14:16:40 +0100 [thread overview]
Message-ID: <fb58125d-334c-e393-74f2-164245297aa5@arm.com> (raw)
In-Reply-To: <CAFiYyc0y3h=QvNJWnG00c5Pc0y7sVDSPL9RejWoxuDu3htjKWA@mail.gmail.com>
On 22/07/2020 13:24, Richard Biener via Gcc-patches wrote:
> On Wed, Jul 22, 2020 at 12:03 PM Andrea Corallo <andrea.corallo@arm.com> wrote:
>>
>> Hi all,
>>
>> I'd like to submit the following two patches implementing a new AArch64
>> specific back-end pass that helps optimize branch-dense code, which can
>> be a bottleneck for performance on some Arm cores. This is achieved by
>> padding out the branch-dense sections of the instruction stream with
>> nops.
>>
>> The original patch was already posted some time ago:
>>
>> https://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg200721.html
>>
>> This follows up splitting as suggested in two patches, rebasing on
>> master and implementing the suggestions of the first code review.
>>
>> This first patch implements the addition of a new RTX instruction class
>> FILLER_INSN, which has been white listed to allow placement of NOPs
>> outside of a basic block. This is to allow padding after unconditional
>> branches. This is favorable so that any performance gained from
>> diluting branches is not paid straight back via excessive eating of
>> nops.
>>
>> It was deemed that a new RTX class was less invasive than modifying
>> behavior in regards to standard UNSPEC nops.
>>
>> 1/2 is requirement for 2/2. Please see this the cover letter of this last
>> for more details on the pass itself.
>
> I wonder if such effect of instructions on the pipeline can be modeled
> in the DFA and thus whether the scheduler could issue (always ready)
> NOPs?
>
> I also wonder whether such optimization is better suited for the assembler
> which should know instruction lengths and alignment in a more precise
> way and also would know whether extra nops make immediates too large
> for pc relative things like short branches or section anchor accesses
> (or whatever else)?
No, the assembler should never spontaneously insert instructions. That
breaks the branch range calculations that the compiler relies upon.
R.
>
> Richard.
>
>> Regards
>>
>> Andrea
>>
>> gcc/ChangeLog
>>
>> 2020-07-17 Andrea Corallo <andrea.corallo@arm.com>
>> Carey Williams <carey.williams@arm.com>
>>
>> * cfgbuild.c (inside_basic_block_p): Handle FILLER_INSN.
>> * cfgrtl.c (rtl_verify_bb_layout): Whitelist FILLER_INSN outside
>> basic blocks.
>> * coretypes.h: New rtx class.
>> * emit-rtl.c (emit_filler_after): New function.
>> * rtl.def (FILLER_INSN): New rtl define.
>> * rtl.h (rtx_filler_insn): Define new structure.
>> (FILLER_INSN_P): New macro.
>> (is_a_helper <rtx_filler_insn *>::test): New test helper for
>> rtx_filler_insn.
>> (emit_filler_after): New extern.
>> * target-insns.def: Add target insn definition.
next prev parent reply other threads:[~2020-07-22 13:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 10:02 Andrea Corallo
2020-07-22 10:09 ` [PATCH 2/2] Aarch64: Add branch diluter pass Andrea Corallo
2020-07-22 10:39 ` Andrew Pinski
2020-07-22 13:53 ` Andrea Corallo
2020-07-22 16:43 ` Segher Boessenkool
2020-07-22 19:45 ` Andrea Corallo
2020-07-23 22:47 ` Segher Boessenkool
2020-07-24 7:01 ` Andrea Corallo
2020-07-24 11:53 ` Segher Boessenkool
2020-07-24 13:21 ` Andrea Corallo
2020-07-24 22:09 ` Segher Boessenkool
2020-07-28 18:55 ` Andrea Corallo
2020-07-28 22:07 ` Segher Boessenkool
2020-07-22 12:24 ` [PATCH 1/2] Add new RTX instruction class FILLER_INSN Richard Biener
2020-07-22 13:16 ` Richard Earnshaw (lists) [this message]
2020-07-22 14:51 ` Andrea Corallo
2020-07-22 18:41 ` Joseph Myers
2020-07-24 21:18 ` Segher Boessenkool
2020-07-26 18:19 ` Eric Botcazou
2020-07-28 19:29 ` Andrea Corallo
2020-08-19 9:13 ` Andrea Corallo
2020-08-19 10:52 ` Richard Sandiford
2020-08-19 17:28 ` Segher Boessenkool
2020-08-19 16:51 ` Segher Boessenkool
2020-08-19 17:47 ` Andrea Corallo
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=fb58125d-334c-e393-74f2-164245297aa5@arm.com \
--to=richard.earnshaw@arm.com \
--cc=andrea.corallo@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.com \
--cc=richard.guenther@gmail.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).