https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94123
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |bergner at gcc dot
gnu.org
--- Comment #8 from Peter Bergner <bergner at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #7)
> Just default rules applied - the bug is new in GCC 10. Since it's also a
> testsuite regression it woudl be nice to at least make that clean. If
> we understand why the regression happens and can live with it we can demote
> it to P2.
So Segher's commit that caused this, added -fsplit-wide-types-early. If you
use -fno-split-wide-types-early then we get the expected code. It's strange
that both Segher's patch and my fix from PR87507 tries to break these TImode
uses up early and somehow, we're tripping over each other. I will continue to
debug this and generate a fix.
That said, I think given there is a work around and that __int128 usage isn't
all that common, that we can probably reduce the priority of this to P2.
