--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-ndk+unsubscribe@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-ndk.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-ndk/6b9f03e3-f8da-4def-88fe-cc535c8e1f03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Which STL?
On Sun, Dec 10, 2017 at 7:16 PM, seal2002 <phann...@gmail.com> wrote:
Hello,
I use std::chrono::microseconds for some stuff in my app. I got some errors with the compilation in arm64 with type use int64_t for some variables. After digging to android-ndk, I realize the type def of int64_t is long long for 32bit but only long in 64bit. I solve that by casting the return of std::chrono::microseconds to int64_t and the compile is fine. But I wonder it is safe to do that ? For long long and use cast to only long type ? Should android ndk check that ?
I use android-ndk-r15c on windows 10 64bit. I already check with android-ndk-r16 but seem it still the same.
Thanks,
seal
--
You received this message because you are subscribed to the Google Groups "android-ndk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-ndk...@googlegroups.com.
#if defined(__LP64__)
typedef long __int64_t;
typedef unsigned long __uint64_t;
#else
typedef long long __int64_t;
typedef unsigned long long __uint64_t;
#endif
To view this discussion on the web visit https://groups.google.com/d/msgid/android-ndk/2e80c1f6-5c39-489c-95b9-f3c4c4055686%40googlegroups.com.