On 1/8/2026 8:28 PM, Peter Bergner wrote:
The Ascalon core implements the full RVA23 profile plus a few other optional
extensions. However, -mcpu=tt-ascalon-d8 option doesn't enable them all.
Add the missing extensions.
Rather than just adding the missing extensions to the already long extension
list, which is pretty unwieldy and unreadable, I made use of the pre-existing
rva23s64 profile and then added the other supported extensions over and above
those included in the profile. This makes it easy for GCC developers to see
that Ascalon is a RVA23 compliant cpu and makes it easier to maintain.
I double checked the ".attribute arch ..." we emit into assembler files and
verified we still get all of the extensions we used to emit, plus we also get
the supported extensions we failed to omit before.
This was regtested on riscv64-linux with no regressions.
Ok for trunk? This should be low risk, since it only affects Ascalon.
Peter
gcc/
* config/riscv/riscv-cores.def (RISCV_CORE)<tt-ascalon-d8>: Add missing
extensions via use of rva23s64 profile and adding zkr, smaia, smmpm,
smnpm, smrnmi, smstateen, ssaia, ssstrict, svadu.
OK. And I think we should just make you the de-facto maintainer for any
ascalon bits and more importantly a reviewer for anything in the risc-v
space. Seems like a good topic for next week's patchwork call.
jeff
