Why isn’t there int128_t?

by

I’ll refer to the C standard; I think the C++ standard inherits the rules for <stdint.h> / <cstdint> from C.

I know that gcc implements 128-bit signed and unsigned integers, with the names __int128 and unsigned __int128 (__int128 is an implementation-defined keyword) on some platforms.

Even for an implementation that provides a standard 128-bit type, the standard does not require int128_t or uint128_t to be defined. Quoting section 7.20.1.1 of the N1570 draft of the C standard:

These types are optional. However, if an implementation provides
integer types with widths of 8, 16, 32, or 64 bits, no padding bits,
and (for the signed types) that have a two’s complement
representation, it shall define the corresponding typedef names.

C permits implementations to defined extended integer types whose names are implementation-defined keywords. gcc’s __int128 and unsigned __int128 are very similar to extended integer types as defined by the standard — but gcc doesn’t treat them that way. Instead, it treats them as a language extension.

In particular, if __int128 and unsigned __int128 were extended integer types, then gcc would be required to define intmax_t and uintmax_t as those types (or as some types at least 128 bits wide). It does not do so; instead, intmax_t and uintmax_t are only 64 bits.

This is, in my opinion, unfortunate, but I don’t believe it makes gcc non-conforming. No portable program can depend on the existence of __int128, or on any integer type wider than 64 bits. And changing intmax_t and uintmax_t would cause serious ABI compatibility problems.

More Related Contents:

  1. Iterator invalidation rules for C++ containers
  2. What’s the difference between “STL” and “C++ Standard Library”?
  3. How to convert an instance of std::string to lower case
  4. std::string formatting like sprintf
  5. What are the mechanics of short string optimization in libc++?
  6. Writing your own STL Container
  7. Library function for Permutation and Combination in C++
  8. Deleting elements from std::set while iterating
  9. Can I take the address of a function defined in standard library?
  10. How to get IOStream to perform better?
  11. std::queue iteration
  12. C++ valarray vs. vector
  13. Forward declare a standard container?
  14. C++ std::vector vs array in the real world
  15. What does string::npos mean in this code?
  16. Why is there no transform_if in the C++ standard library?
  17. C++ Filehandling: Difference between ios::app and ios::ate?
  18. Assign a nullptr to a std::string is safe?
  19. GCC linker can’t find standard library?
  20. Why is the STL so heavily based on templates instead of inheritance?
  21. std::lexical_cast – is there such a thing?
  22. Why was std::pow(double, int) removed from C++11?
  23. How similar are Boost.Filesystem and the C++ standard filesystem library?
  24. Why do we need to tie std::cin and std::cout?
  25. How can I use a std::valarray to store/manipulate a contiguous 2D array?
  26. Why is operator!= removed in C++20 for many standard library types?
  27. Why do people use __ (double underscore) so much in C++
  28. Qt 5.1.1: Application failed to start because platform plugin “windows” is missing
  29. Memory alignment in C-structs
  30. When to use extern “C” in C++? [duplicate]

Leave a Comment