https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622
--- Comment #32 from Jonathan Wakely ---
Hmm, yes. Well I think we can at least make std::is_integral<__int128> true,
which will remove once source of surprises for users.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622
--- Comment #31 from joseph at codesourcery dot com ---
It can be an extended integer type in C2x, but then stdint.h would be
required to have int128_t / uint128_t / int_least128_t / uint_least128_t
typedefs, and integer constant suffixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622
--- Comment #30 from Jonathan Wakely ---
(In reply to John Maddock from comment #26)
> (In reply to jos...@codesourcery.com from comment #25)
> > On Thu, 20 Nov 2014, john at johnmaddock dot co.uk wrote:
> >
> > > While we're opening cans of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622
--- Comment #28 from Andrew Pinski ---
I suspect this has now been fixed with the additional of full _Float128 support
in the C++ front-end and the library work.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43622
Marc Glisse glisse at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last