From: Joseph Myers <joseph@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [RFC] <sys/tagged-address.h>: An API for tagged address
Date: Thu, 11 Feb 2021 20:28:28 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2102112022390.2915723@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20210211173711.71736-1-hjl.tools@gmail.com>
On Thu, 11 Feb 2021, H.J. Lu via Libc-alpha wrote:
> An API for tagged address:
Please write a longer commit message, discussing what "tagged address" is,
which architectures have such a thing (the API should try to cover
whatever is common between architectures as far as possible - is this
meant to relate to AArch64 MTE, how does it relate to the MTE code we
already have in glibc, what corresponding features are involved on other
architectures?) and what the API is intended to be useful for. A new API
also needs additions to the manual and NEWS - again, explaining things at
the user level.
The header naming suggests installed headers, but you don't appear to be
installing them.
I don't see anything architecture-specific about the build logic, so I'd
expect all libc.abilist files to have the new functions rather than just a
few.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-02-11 20:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 17:37 H.J. Lu
2021-02-11 20:28 ` Joseph Myers [this message]
2021-02-11 21:39 ` H.J. Lu
2021-02-12 9:43 ` Florian Weimer
2021-02-12 13:06 ` H.J. Lu
2021-02-17 18:43 ` H.J. Lu
2021-02-17 21:58 ` H.J. Lu
2021-02-18 13:24 ` Szabolcs Nagy
2021-02-18 13:28 ` Florian Weimer
2021-02-18 13:50 ` Szabolcs Nagy
2021-02-18 22:32 ` H.J. Lu
2021-02-22 8:27 ` Szabolcs Nagy
2021-02-22 13:57 ` H.J. Lu
2021-02-18 13:17 ` Szabolcs Nagy
2021-02-18 13:21 ` Florian Weimer
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=alpine.DEB.2.22.394.2102112022390.2915723@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.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).