-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating coredistools #414
Comments
@BruceForstall
It's ok for LoongArch. |
Also @dotnet/arm64-contrib |
Thanks for adding RISC-V disasm to the standard set. Clang 19 should be ok. EDIT: I'll check if "+all" works now for RISC-V |
Not really from RISC-V. We will be adding RVA22 profile extensions somewhere in 2025, but RV64GC is the correct set for now. |
Nope, it's AArch64 only: But while I'm here, I'll add more extensions for RISC-V to future-proof. |
Add extensions of ratified RISC-V application profiles (the unprivileged side). JIT doesn't emit code for newly added extensions yet, this is to future-proof since coredistools are rebuilt infrequently. See #414 (comment) for context. Part of dotnet/runtime#84834, cc @dotnet/samsung @BruceForstall
Hi Bruce, I will check internally and get back to you on ISA support in LLVM latest. I believe by just using latest we should be fine, but will confirm whether we have any pending work. |
@BruceForstall latest LLVM disassembler should have full support for APX and AVX10.2. I think we are good. |
What should be included in the next update of the coredistools library (used for x86/x64 GC stress, R2RDump disassembly, superpmi asm diffs, RyuJIT "late disassembler", ILC (?), and possibly more)?
Some proposals:
Cordistools.cpp currently tweaks the "features string" when creating the disassembler, to create a better set of ISAs for disassembly:
Notably, when this was done, "+all" for arm64 was not in "great" shape.
Is this still the correct set, for LLVM 19.1.0 (and beyond)?
Is there any pressing need to either update coredistools, or wait to update it?
Comments?
@dotnet/jit-contrib @dotnet/samsung @shushanhf @dotnet/crossgen-contrib @khushal1996 @DeepakRajendrakumaran @anthonycanino
The text was updated successfully, but these errors were encountered: