From: Edwin Lu <ewlu@rivosinc.com>
To: Jeff Law <jeffreyalaw@gmail.com>, gcc-patches@gcc.gnu.org
Cc: gnu-toolchain@rivosinc.com
Subject: Re: [RFC] RISC-V: Handle new types in scheduling descriptions
Date: Tue, 10 Oct 2023 14:18:40 -0700 [thread overview]
Message-ID: <d0ddf3dc-6b12-4cbf-aed8-314b6c5a9ec9@rivosinc.com> (raw)
Message-ID: <20231010211840.MrrNuhrwNGpz-EI42oiSywTvSvZv0VNzF4pjsXUA_Bs@z> (raw)
In-Reply-To: <101c89cb-df98-4e12-be41-5c20870b6d7d@gmail.com>
On 10/10/2023 10:11 AM, Jeff Law wrote:
>
>
> On 10/9/23 15:02, Edwin Lu wrote:
>> Now that every insn is guaranteed a type, we want to ensure the types are
>> handled by the existing scheduling descriptions.
>>
>> There are 2 approaches I see:
>> 1. Create a new pipeline intended to eventually abort (sifive-7.md)
>> 2. Add the types to an existing pipeline (generic.md)
>>
>> Which approach do we want to go with? If there is a different approach we
>> want to take instead, please let me know as well.
>>
>> Additionally, should types associated with specific extensions
>> (vector, crypto, etc) have specific pipelines dedicated to them?
>>
>> * config/riscv/generic.md: update pipeline
>> * config/riscv/sifive-7.md (sifive_7): update pipeline
>> (sifive_7_other):
> I'd largely expect that we look at an unhandled type and first look to
> see if its properties roughly fit into an existing define_insn_unit. If
> so, just add it to the existing unit. Otherwise we end up needing to
> create another unit.
>
The main types that were added that are not associated with any
extension would be "trap" type and the "cbo" (cache block operation)
type. I have added these types to an existing pipeline in the generic.md
file.
For the vector extension, I don't believe the existing pipelines would
support those operations. Should I create the pipelines for now?
> What would be really interesting would be to see if we can get the
> scheduler to indicate that it's trying to schedule an insn that doesn't
> have a reservation. ie, our backend tells us if we have an insn with
> no type, the next step is to see if we have a type with no
> units/reservations.
>
>
> Jeff
>
Do you happen to have any idea on how to do this or if there are any
existing mechanisms I should look at? I have been searching around the
docs to see if there was any way to tell which pipeline (if any) an
instruction is using when it is not included under a reservation without
any luck.
Edwin
next prev parent reply other threads:[~2023-10-10 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 21:02 Edwin Lu
2023-10-10 17:11 ` Jeff Law
2023-10-10 21:18 ` Edwin Lu [this message]
2023-10-10 21:18 ` Edwin Lu
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=d0ddf3dc-6b12-4cbf-aed8-314b6c5a9ec9@rivosinc.com \
--to=ewlu@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu-toolchain@rivosinc.com \
--cc=jeffreyalaw@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).