Bruno Haible <br...@clisp.org> writes:
> Why not CFLAGS='-std=gnu99' ? [1]
>
> Compiler options like -std=c99 (compilation for ISO C without extensions)
> or -D_POSIX_C_SOURCE or -D_XOPEN_SOURCE=500 (enable older POSIX functions,
> but not newer ones) are fine when you compile highly portable programs,
> like TeX or MetaFont or a Pascal to C converter. But for a package like
> Guile, that includes a garbage collector and a JIT compiler and therefore
> needs to access a lot of system facilities, it is just not a reasonable
> choice.
Yes, CFLAGS='-std=gnu99' is obviously the better choice. I just wrote
CFLAGS='-std=c99' instinctively while thinking about the
int foo () == int foo (void) changes in C23. I realized the issue
quickly afterwards though, so not much time lost.
>> Wouldn't it be better to use '__asm__' here and in the other functions
>> using inline assembly?
>
> IIRC, I tried that, and one of the compilers understood only 'asm', not
> '__asm__'.
Ah, I see. That makes sense. Current code is fine with me then.
I think autoconf-archive has something like:
for keyword in __asm__ __asm asm; do
# Do a test program
done
Which we could do if it ever becomes a problem. But unless someone
reports their compiler choking, I think it is fine to ignore.
Collin
