From: Andreas Schwab <schwab@suse.de>
To: Szabolcs Nagy via Libc-alpha <libc-alpha@sourceware.org>
Cc: David Malcolm <dmalcolm@redhat.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
gcc@gcc.gnu.org, Mir Immad <mirimnan017@gmail.com>
Subject: Re: Adding file descriptor attribute(s) to gcc and glibc
Date: Wed, 13 Jul 2022 10:46:04 +0200 [thread overview]
Message-ID: <mvmmtddienn.fsf@suse.de> (raw)
In-Reply-To: <Ys6ENUYqC2Qm5MUL@arm.com> (Szabolcs Nagy via Libc-alpha's message of "Wed, 13 Jul 2022 09:37:09 +0100")
On Jul 13 2022, Szabolcs Nagy via Libc-alpha wrote:
> note that glibc headers have to be namespace clean so it
> would be more like
>
> __attribute__((__fd_argument (__access, 1)))
> __attribute__((__fd_argument (__read, 1)))
> __attribute__((__fd_argument (__write, 1)))
>
> so it would be even shorter to write
>
> __attribute__((__fd_argument_access (1)))
> __attribute__((__fd_argument_read (1)))
> __attribute__((__fd_argument_write (1)))
The attribute will need to be hidden behind a macro anyway, like it is
done with most other attributes now.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2022-07-13 8:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 17:31 [PATCH] filedescriptor attribute Immad Mir
2022-07-12 17:33 ` Mir Immad
2022-07-12 22:16 ` Adding file descriptor attribute(s) to gcc and glibc David Malcolm
2022-07-12 22:25 ` David Malcolm
2022-07-13 8:37 ` Szabolcs Nagy
2022-07-13 8:46 ` Andreas Schwab [this message]
2022-07-13 12:05 ` Florian Weimer
2022-07-13 13:33 ` David Malcolm
2022-07-13 14:01 ` Florian Weimer
2022-07-13 16:55 ` David Malcolm
2022-07-14 8:30 ` Szabolcs Nagy
2022-07-14 15:22 ` David Malcolm
2022-07-14 17:07 ` Paul Eggert
2022-07-13 16:56 ` Mir Immad
2022-07-13 19:29 ` David Malcolm
2022-07-13 12:57 ` David Malcolm
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=mvmmtddienn.fsf@suse.de \
--to=schwab@suse.de \
--cc=dmalcolm@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=mirimnan017@gmail.com \
--cc=szabolcs.nagy@arm.com \
/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).