https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98442
H.J. Lu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98442
--- Comment #4 from Richard Biener ---
Using ymm might also trigger dynamic stack realignment if we ever spill, also
using ymm can be slower when the memory is unaligned (and/or when the CPU
has split AVX support only). It will also require vzer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98442
--- Comment #3 from H.J. Lu ---
(In reply to H.J. Lu from comment #2)
> Please take a look at users/hjl/pieces/master branch:
>
> https://gitlab.com/x86-gcc/gcc/-/tree/users/hjl/pieces/master
>
> You may get some ideas.
I got
[hjl@gnu-cfl-1 g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98442
H.J. Lu changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98442
--- Comment #1 from Hongtao.liu ---
>
> Define TARGET_USE_BY_PIECES_INFRASTRUCTURE_P for i386?
It's actually determined by MOV_MAX_PIECES and related to MAX_FIXED_MODE_SIZE
??? We should use TImode in 32-bit mode and use OImode or XImode
