On 3/25/25 8:04 AM, Yangyu Chen wrote:
On 25/3/2025 21:23, Kito Cheng wrote:
Will it only cause issues with this patch
https://gcc.gnu.org/pipermail/gcc-patches/2025-March/678918.html
Yes. But I think we can merge this first.
But if this patch doesn't fix a regression or possibly a correc
On 25/3/2025 21:23, Kito Cheng wrote:
Will it only cause issues with this patch
https://gcc.gnu.org/pipermail/gcc-patches/2025-March/678918.html
Yes. But I think we can merge this first.
Thanks,
Yangyu Chen
or will it cause problems with the current trunk as well?
If the latter one, coul
Will it only cause issues with this patch
https://gcc.gnu.org/pipermail/gcc-patches/2025-March/678918.html
or will it cause problems with the current trunk as well?
If the latter one, could you provide a case for that?
Thanks :)
On Tue, Mar 25, 2025 at 7:15 PM Yangyu Chen wrote:
>
> We don't ne
We don't need to add priority in ASM name mangling, keeping this might
cause an issue if we call another MV clone directly but only one place
has the priority declared.
gcc/ChangeLog:
* config/riscv/riscv.cc (riscv_mangle_decl_assembler_name): Remove
priority in fmv asm name mangl