From: Edwin Lu <ewlu@rivosinc.com>
To: Mike Stump <mikestump@comcast.net>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, gnu-toolchain@rivosinc.com
Subject: Re: [Committed] testsuite: Add support for scanning assembly with comparitor
Date: Fri, 16 Feb 2024 10:19:59 -0800 [thread overview]
Message-ID: <acba04e2-0c29-414e-b36a-32fd1828f2cf@rivosinc.com> (raw)
In-Reply-To: <EB675D46-F3B6-40AE-836E-6ED5FA427A94@comcast.net>
Thanks! Committed
Edwin
On 2/15/2024 9:27 AM, Mike Stump wrote:
> On Feb 12, 2024, at 11:38 AM, Edwin Lu <ewlu@rivosinc.com> wrote:
>> There is currently no support for matching at least x lines of assembly
>> (only scan-assembler-times). This patch would allow setting upper or lower
>> bounds.
>>
>> Use case: using different scheduler descriptions and/or cost models will change
>> assembler output. Testing common functionality across tunes would require a
>> separate testcase per tune since each assembly output would be different. If we
>> know a base number of lines should appear across all tunes (i.e. testing return
>> values: we expect at minimum n stores into register x), we can lower-bound the
>> test to search for scan-assembler-bound {RE for storing into register x} >= n.
>> This avoids artificially inflating the scan-assembler-times expected count due
>> to the assembler choosing to perform extra stores into register x (using it as
>> a temporary register).
>>
>> The testcase would be more robust to cpu/tune changes at the cost of not being
>> as granular towards specific cpu tuning.
> I didn't see an Ok? Just in case you forgot, yes, this is ok.
prev parent reply other threads:[~2024-02-16 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 19:38 [PATCH] " Edwin Lu
2024-02-15 17:27 ` Mike Stump
2024-02-16 18:19 ` Edwin Lu [this message]
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=acba04e2-0c29-414e-b36a-32fd1828f2cf@rivosinc.com \
--to=ewlu@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=mikestump@comcast.net \
/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).