`zig cc -target arm-linux-gnueabihf` sets `__ILP32__`

[tmm1]

Zig Version

0.15.1

Steps to Reproduce and Observed Behavior

❯ zig cc -target arm-linux-gnueabihf -E - <<<'__ILP32__ __arm__'
# 1 "<stdin>"
# 1 "<built-in>" 1
# 1 "<built-in>" 3
# 417 "<built-in>" 3
# 1 "<command line>" 1
# 1 "<built-in>" 2
# 1 "<stdin>" 2
1 1

Expected Behavior

Expect openssl/config/bio_asm.h to work during nodejs/v8 compile w/ arm target

#if defined(OPENSSL_LINUX) && defined(__i386__)
# include "./archs/linux-elf/asm/include/openssl/bio.h"
#elif defined(OPENSSL_LINUX) && defined(__ILP32__)
# include "./archs/linux-x32/asm/include/openssl/bio.h"
#elif defined(OPENSSL_LINUX) && defined(__x86_64__)
# include "./archs/linux-x86_64/asm/include/openssl/bio.h"
#elif defined(OPENSSL_LINUX) && defined(__arm__)
# include "./archs/linux-armv4/asm/include/openssl/bio.h"
#elif defined(OPENSSL_LINUX) && defined(__aarch64__)
# include "./archs/linux-aarch64/asm/include/openssl/bio.h"

[alexrp]

❯ arm-linux-gnueabihf-gcc -dM -E - < /dev/null | grep ILP32
❯ clang --target=arm-linux-gnueabihf -dM -E - < /dev/null | grep ILP32
#define _ILP32 1
#define __ILP32__ 1

This is a Clang bug. We don't do anything in the Zig driver to define that macro.

That said, the Node.js code there is silly because __ILP32__ isn't exclusive to x32 even in GCC. If they want to test for x32, they should do defined(OPENSSL_LINUX) && defined(__x86_64__) && defined(__ILP32__).