From: Eric Blake <eblake@redhat.com>
To: Andreas Schwab <schwab@linux-m68k.org>,
Eric Blake via Libc-alpha <libc-alpha@sourceware.org>
Cc: Carol Bouchard <cbouchar@redhat.com>,
Bruno Haible <bruno@clisp.org>,
"austin-group-l@opengroup.org" <austin-group-l@opengroup.org>,
bug-m4@gnu.org
Subject: Re: SIGSTKSZ is now a run-time variable
Date: Tue, 9 Mar 2021 09:48:47 -0600 [thread overview]
Message-ID: <d84de10b-c528-19f7-353a-397cfedeeb2c@redhat.com> (raw)
In-Reply-To: <87y2ew8i1w.fsf@igel.home>
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
next prev parent reply other threads:[~2021-03-09 15:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1841269.IEpri3ZHvQ@omega>
2021-03-09 15:23 ` Eric Blake
2021-03-09 15:26 ` Andreas Schwab
2021-03-09 15:48 ` Eric Blake [this message]
2021-03-09 19:58 ` Bruno Haible
2021-03-09 21:05 ` H.J. Lu
[not found] ` <20210309211735.GW19922@dragon.sl.home>
2021-03-16 19:46 ` Carol Bouchard
2021-03-26 12:46 ` Carol Bouchard
2021-03-09 15:46 ` Zack Weinberg
[not found] <832918739.1734727.1615306471320.ref@mail.yahoo.com>
2021-03-09 16:14 ` shwaresyst
2021-03-09 19:33 ` Paul Eggert
2021-03-09 19:34 ` Eric Blake
2021-03-09 20:12 ` Eric Blake
[not found] <1569476484.1894162.1615325397167.ref@mail.yahoo.com>
2021-03-09 21:29 ` shwaresyst
2021-03-09 23:58 ` H.J. Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d84de10b-c528-19f7-353a-397cfedeeb2c@redhat.com \
--to=eblake@redhat.com \
--cc=austin-group-l@opengroup.org \
--cc=bruno@clisp.org \
--cc=bug-m4@gnu.org \
--cc=cbouchar@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).