Community
Participate
Working Groups
Therefore every function prototype containing any type derived from __int64 doesn't match, e.g. on Win64 time_t -> __time64_t -> __int64 Regards, Gert
I define macros like this (in Project properties, Paths and symbols) __int64 : long long __int32 : int __int16 : short __int8 : char It does seems to work pretty well in my code base. Perhaps we should define them by default to these values? What do you think?
Let's do this until we have a VC specific parser. I'll also define __forceinline as __inline, it has given me trouble as well.
Fixed in master and 8_1. https://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=1b2b5e5cd4045da1861ecb9088fc02e468e188af
*** cdt git genie on behalf of Marc-Andre Laperle *** Bug 383773 - __int64 is not detected as valid type with MSVC toolchain [*] http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=1b2b5e5cd4045da1861ecb9088fc02e468e188af
*** cdt git genie on behalf of Marc-Andre Laperle *** Bug 383773 - __int64 is not detected as valid type with MSVC toolchain [*] http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=92376ee191ab48f1fc2030704977d3a62c13ccf8
*** Bug 69630 has been marked as a duplicate of this bug. ***