From: "Cristian Rodríguez" <cristian@rodriguez.im>
To: Xi Ruoyao <xry111@xry111.site>
Cc: Joe Simmons-Talbott <josimmon@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] posix: Deprecate group_member for Linux
Date: Wed, 4 Oct 2023 11:18:54 -0300 [thread overview]
Message-ID: <CAPBLoAcai=Vmf2ZgwXUie28Ank_6HejjhsFeOHD1fMHcyYsW2Q@mail.gmail.com> (raw)
In-Reply-To: <4b80d08c6263790f1694085c0f5a862c883fbd67.camel@xry111.site>
[-- Attachment #1: Type: text/plain, Size: 286 bytes --]
On Wed, Oct 4, 2023 at 10:06 AM Xi Ruoyao <xry111@xry111.site> wrote:
>
> Maybe `__attribute_deprecated_msg__ ("may overflow the stack")` is
> better? And should we have an alternate interface to replace it?
>
>
or maybe just use malloc __fortify_fail ("") if that fails ?
next prev parent reply other threads:[~2023-10-04 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 16:20 Joe Simmons-Talbott
2023-10-04 12:56 ` Joe Simmons-Talbott
2023-10-04 13:06 ` Xi Ruoyao
2023-10-04 14:18 ` Cristian Rodríguez [this message]
2023-10-16 17:00 ` Joe Simmons-Talbott
2023-10-16 16:52 ` Joe Simmons-Talbott
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='CAPBLoAcai=Vmf2ZgwXUie28Ank_6HejjhsFeOHD1fMHcyYsW2Q@mail.gmail.com' \
--to=cristian@rodriguez.im \
--cc=josimmon@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=xry111@xry111.site \
/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).