http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53353
Jakub Jelinek jakub at gcc dot gnu.org changed:
What|Removed |Added
CC||jakub at gcc dot
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53353
Andrew Pinski pinskia at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53353
--- Comment #2 from Steven Fuerst svfuerst at gmail dot com 2012-05-15
01:54:46 UTC ---
Obviously a __int128_t fits in two registers. The bug is that gcc doesn't
warn/error about code mistakenly trying to fit it into one. Instead, gcc
generates
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53353
--- Comment #3 from Andrew Pinski pinskia at gcc dot gnu.org 2012-05-15
02:02:23 UTC ---
(In reply to comment #2)
Obviously a __int128_t fits in two registers. The bug is that gcc doesn't
warn/error about code mistakenly trying to fit it into
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53353
--- Comment #4 from Steven Fuerst svfuerst at gmail dot com 2012-05-15
02:09:05 UTC ---
Actually, it is the rax:rdx pair that is most likely. ax:dx only has 32 bits.
rax:rdx is specified by the 'A' constraint, the only gpr option that is 128
