On Wed, 04 Sep 2024 19:24:41 PDT (-0700), Kito Cheng wrote:
Just remember adding a system wide vector calling convention has wide
compatible issues we need to worry about, like jump buf (for
setjmp/longjmp) will need to keep vector status, it doesn't need to
keep before since all vectors are call
Just remember adding a system wide vector calling convention has wide
compatible issues we need to worry about, like jump buf (for
setjmp/longjmp) will need to keep vector status, it doesn't need to
keep before since all vectors are call-clobber by default.
Also that may cause performance issue fo
On 9/4/24 2:26 PM, Palmer Dabbelt wrote:
Now that we've got the riscv_vector_cc attribute it's pretty much free
to add a system-wide ABI -- at least in terms of implementation. So
this just adds a new ABI command-line value that defaults to enabling
the vector calling convention, essentially
On Wed, 04 Sep 2024 13:26:11 PDT (-0700), Palmer Dabbelt wrote:
Now that we've got the riscv_vector_cc attribute it's pretty much free
to add a system-wide ABI -- at least in terms of implementation. So
this just adds a new ABI command-line value that defaults to enabling
the vector calling conv
Now that we've got the riscv_vector_cc attribute it's pretty much free
to add a system-wide ABI -- at least in terms of implementation. So
this just adds a new ABI command-line value that defaults to enabling
the vector calling convention, essentially the same as scattering the
attribute on every
