[Bug fortran/43685] libgfortran: Consider using __int128

[fxcoudert at gcc dot gnu dot org]

--- Comment #1 from fxcoudert at gcc dot gnu dot org  2010-06-09 12:01 
---
I don't understand what you mean by that: currently, we have the following
typedefs on platforms which support a 128-bit int type:

  typedef __int128_t GFC_INTEGER_16;
  typedef __uint128_t GFC_UINTEGER_16;

I don't think it changes anything to put __int128 instead of __int128_t. This
is a special case anyway, because other kinds use the stdint.h name: int8_t,
int16_t, int32_t and int64_t.


-- 

fxcoudert at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||fxcoudert at gcc dot gnu dot
   ||org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43685

[Bug fortran/43685] libgfortran: Consider using __int128

[burnus at gcc dot gnu dot org]

--- Comment #2 from burnus at gcc dot gnu dot org  2010-06-09 12:41 ---
Close as WONTFIX.

The int128 changes still do not offer to enter the integer directly (instead of
using 123L with  shifts)

And one issue was fixed as part of
  http://gcc.gnu.org/viewcvs?view=revisionrevision=157407
(in libgfortran.h).


-- 

burnus at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution||WONTFIX


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43685