From: Richard Sandiford <richard.sandiford@arm.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: Wilco Dijkstra via Gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][AArch64] Improve immediate expansion [PR106583]
Date: Fri, 07 Oct 2022 15:49:22 +0100 [thread overview]
Message-ID: <mptfsfzheod.fsf@arm.com> (raw)
In-Reply-To: <AS4PR08MB7901024035054329DE59A58F835F9@AS4PR08MB7901.eurprd08.prod.outlook.com> (Wilco Dijkstra's message of "Fri, 7 Oct 2022 14:48:34 +0100")
Wilco Dijkstra <Wilco.Dijkstra@arm.com> writes:
> Hi Richard,
>
>>> Yes, with a more general search loop we can get that case too -
>>> it doesn't trigger much though. The code that checks for this is
>>> now refactored into a new function. Given there are now many
>>> more calls to aarch64_bitmask_imm, I added a streamlined internal
>>> entry point that assumes the input is 64-bit.
>>
>> Sounds good, but could you put it before the mode version,
>> to avoid the forward declaration?
>
> I can swap them around but the forward declaration is still required as
> aarch64_check_bitmask is 5000 lines before aarch64_bitmask_imm.
OK, how about moving them both above aarch64_check_bitmask?
Richard
next prev parent reply other threads:[~2022-10-07 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 17:22 Wilco Dijkstra
2022-10-05 8:42 ` Richard Sandiford
2022-10-06 17:29 ` Wilco Dijkstra
2022-10-07 13:17 ` Richard Sandiford
2022-10-07 13:48 ` Wilco Dijkstra
2022-10-07 14:49 ` Richard Sandiford [this message]
2022-10-12 14:57 ` Wilco Dijkstra
2022-10-19 15:33 ` Wilco Dijkstra
2022-10-20 9:31 ` Richard Sandiford
2022-10-20 12:23 ` Wilco Dijkstra
2022-10-21 9:20 ` Richard Sandiford
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=mptfsfzheod.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=gcc-patches@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: 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).