https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81673
Martin Jambor changed:
What|Removed |Added
Depends on||80689
--- Comment #5 from Martin Jambor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81673
--- Comment #4 from Richard Biener ---
(In reply to Martin Jambor from comment #3)
> (In reply to Andrew Pinski from comment #1)
> > What happens if you use -march=intel.
>
> With -mtune=intel, the lower half of the vector is moved directly
Tha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81673
--- Comment #3 from Martin Jambor ---
(In reply to Andrew Pinski from comment #1)
> What happens if you use -march=intel.
With -mtune=intel, the lower half of the vector is moved directly
whereas the upper one is still done through the stack:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81673
Martin Jambor changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81673
--- Comment #1 from Andrew Pinski ---
What happens if you use -march=intel. Maybe the cost should have adjusted only
for the case where moving between the register set is cheap (I forgot the
internal tuning name for this case).
