diff options
author | Brad Larson <bklarson@gmail.com> | 2017-08-10 11:42:36 -0500 |
---|---|---|
committer | Brad Larson <bklarson@gmail.com> | 2017-08-10 14:47:13 -0500 |
commit | 1b423474fd8ec6beab8d51bbc73b7756960ce2d6 (patch) | |
tree | 9717ecc9d1cebdaefecd6adddba75137cb5ee805 /conformance/failure_list_csharp.txt | |
parent | 35db2675b418ea105ef89f88fd1bf0257eb8a3ff (diff) | |
download | protobuf-1b423474fd8ec6beab8d51bbc73b7756960ce2d6.tar.gz protobuf-1b423474fd8ec6beab8d51bbc73b7756960ce2d6.tar.bz2 protobuf-1b423474fd8ec6beab8d51bbc73b7756960ce2d6.zip |
Clean up typedefs for Atomic32/Atomic64
The typedefs for Atomic32 and Atomic64 were sometimes causing
Atomic32 to be an int32 rather than an intptr_t on 32-bit platforms.
On some of these platforms (ARM/CortexM building with GCC 6 in one
case) int32 is a long int, while intptr_t is an int, which causes a
compiler error even though long int and int are both 4 bytes.
Having Atomic32 always be intptr_t on 32-bit platforms and Atomic64
always be intptr_t on 64-bit platforms should resolve any of these
types of errors.
Diffstat (limited to 'conformance/failure_list_csharp.txt')
0 files changed, 0 insertions, 0 deletions