Numeric_limits doesn't understand 64 bit integers

Question

If you run the following code, you will find that Forte 6 Update 2 (patched) thinks that the maximum value of a 64 bit integer is zero. The same results with long long or unsigned long long.
#include <limits>
#include <iostream>
#include <inttypes.h>
using namespace std;
int main(int argc, char * argv[])
   std::cout << "int32_t: " << numeric_limits<int32_t>::max() << std::endl;
   std::cout << "uint32_t: " << numeric_limits<uint32_t>::max() << std::endl;
   std::cout << "int64_t: " <<numeric_limits<int64_t>::max() << std::endl;
   std::cout << "uint64_t: " <<numeric_limits<uint64_t>::max() << std::endl;
   std::cout << "long long: " <<numeric_limits<long long>::max() << std::endl;
   std::cout << "unsigned long long: " <<numeric_limits<unsigned long long>::max() << std::endl;
   return 0;
}Results:
int32_t: 2147483647
uint32_t: 4294967295
int64_t: 0
uint64_t: 0
long long: 0
unsigned long long: 0

Answer 1

It seems you see a zero return value because the default implementation of numeric_limits lacks definitions for these larger data types. The man page for numeric_limits(3C++) shows this. The list of specializations at the top omits the types for which a zero result is obtained. The zero return value is therefore a "false" condition.
This works with -library=stlport4, however, presumably because the STLport4 implementation has specializations for all of these types:
# CC -library=stlport4 -o test test.cc
# test
int32_t: 2147483647
uint32_t: 4294967295
int64_t: 9223372036854775807
uint64_t: 18446744073709551615
long long: 9223372036854775807
unsigned long long: 18446744073709551615
With FD6u2, you can follow the procedure in Chapter 12 of the C++ User's Guide to replace the default implementation with STLport or another 3rd-party
implementation.
- Rose