KWSys: __int64 and long long may be same type in specialization

For the specialization of hash<>(), the types long long and __int64
may be the same type. While the CMakeLists indicate that if __int64 is
a alias for another type the it will not be enabled, on mingw they
both appear to be the same type and enabled.

This patch only enable specialization for long long OR __int64 to
avoid the potential conflict.

Author: Bradley Lowekamp <blowekamp@mail.nih.gov>
Change-Id: I813a9ac008b296fab5a369c48e6dd5460fd0c035
This commit is contained in:
Brad King 2011-08-09 18:03:09 -04:00
parent 4675f5d204
commit c04613a55d
1 changed files with 3 additions and 4 deletions

View File

@ -110,6 +110,7 @@ struct hash<unsigned long> {
size_t operator()(unsigned long __x) const { return __x; }
};
// use long long or __int64
#if @KWSYS_NAMESPACE@_USE_LONG_LONG
@KWSYS_NAMESPACE@_CXX_DEFINE_SPECIALIZATION
struct hash<long long> {
@ -120,9 +121,7 @@ struct hash<long long> {
struct hash<unsigned long long> {
size_t operator()(unsigned long long __x) const { return __x; }
};
#endif
#if @KWSYS_NAMESPACE@_USE___INT64
#elif @KWSYS_NAMESPACE@_USE___INT64
@KWSYS_NAMESPACE@_CXX_DEFINE_SPECIALIZATION
struct hash<__int64> {
size_t operator()(__int64 __x) const { return __x; }
@ -131,7 +130,7 @@ struct hash<__int64> {
struct hash<unsigned __int64> {
size_t operator()(unsigned __int64 __x) const { return __x; }
};
#endif
#endif // use long long or __int64
} // namespace @KWSYS_NAMESPACE@