From: "H.J. Lu" <hjl.tools@gmail.com>
To: Bruno Haible <bruno@clisp.org>
Cc: Eric Blake <eblake@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>,
Carol Bouchard <cbouchar@redhat.com>,
Andreas Schwab <schwab@linux-m68k.org>,
bug-m4@gnu.org,
"austin-group-l@opengroup.org" <austin-group-l@opengroup.org>
Subject: Re: SIGSTKSZ is now a run-time variable
Date: Tue, 9 Mar 2021 13:05:22 -0800 [thread overview]
Message-ID: <CAMe9rOrYmwXSa-OTMzK_Lv2tsSngEWA6zpGm52dsNwOh6fXa6g@mail.gmail.com> (raw)
In-Reply-To: <13030663.F5dv5Vxd0a@omega>
On Tue, Mar 9, 2021 at 12:27 PM Bruno Haible <bruno@clisp.org> wrote:
>
> Eric Blake wrote:
> > 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.
>
> Thanks for opening the discussion, Eric.
>
> Here are a couple of questions, to understand the motivation and the possible
> alternative solutions to the problem:
>
> 1) As far as I understand, the issue occurs with certain x86 or x86_64
> processors.
>
> 1.1) What has been the value of MINSIGSTKSZ on x86 and x86_64 so far?
It is 2048 bytes in glibc 2.32.
> 1.2) What value of MINSIGSTKSZ is needed for AVX-512F support?
For i686, it is 3628 bytes. For x86-64, it is 3212 bytes.
> 1.3) Will the trend to larger MINSIGSTKSZ values continue for Intel
> processors?
With 8 1K Tile registers, we need another 8K. I can't tell you how big
we will need in 10 years.
--
H.J.
next prev parent reply other threads:[~2021-03-09 21:05 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
2021-03-09 19:58 ` Bruno Haible
2021-03-09 21:05 ` H.J. Lu [this message]
[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=CAMe9rOrYmwXSa-OTMzK_Lv2tsSngEWA6zpGm52dsNwOh6fXa6g@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=austin-group-l@opengroup.org \
--cc=bruno@clisp.org \
--cc=bug-m4@gnu.org \
--cc=cbouchar@redhat.com \
--cc=eblake@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).