On 3/9/21 9:26 AM, Andreas Schwab wrote: > On Mär 09 2021, Eric Blake via Libc-alpha wrote: > >> The question becomes whether glibc is in violation of POSIX for having >> made the change, or whether POSIX needs to be amended to allow SIGSTKSZ >> to be non-preprocessor-safe and/or non-constant. > > POSIX already allows non-preprocessor-safe.
True, but expanding 'SIGSTKSZ' to 'sysconf (_SC_SIGSTKSZ)' is not a symbolic constant., as it is not "a compile-time constant expression with an integer type', per definition 3.380. Looks like this discussion is happening in parallel in: https://sourceware.org/bugzilla/show_bug.cgi?id=20305 I can open a defect against POSIX if we decide that is needed, but want some consensus first on whether it is glibc's change that went too far, or POSIX's requirements that are too restrictive for what glibc wants to do. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org
