From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Szabolcs Nagy <Szabolcs.Nagy@arm.com>, "H.J. Lu" <hjl.tools@gmail.com>
Cc: Szabolcs Nagy <nsz@port70.net>,
"H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH] aarch64: MTE compatible strchrnul
Date: Fri, 5 Jun 2020 08:45:33 +0000 [thread overview]
Message-ID: <DB8PR08MB50364FDFC5752BD36500E27D83860@DB8PR08MB5036.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20200605073823.GM21536@arm.com>
Hi,
>> Should we add a marker to indicate that an object file is
>> mte compatible?
>
> i think we will need a marking for 'compatible with tagged
> pointers' (on aarch64 pointer that's a new opt-in kernel abi
> and user code may use the top byte of pointers) and another
> one for 'compatible with 16byte granules'.
>
> e.g. the old string asm would have the first marking but not
> the second one.
I don't see how adding different markings would help. String functions
which are not MTE compatible simply cannot be used if MTE is enabled,
and if they are not fixed or ifunced then all of GLIBC is not compatible
with MTE.
Compatibility is a dynamic property, ie. an incompatible string function is
perfectly fine if it is ifunced. So having various different markings is not useful.
Either way all of this is unrelated to these patches.
Cheers,
Wilco
next prev parent reply other threads:[~2020-06-05 8:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 9:43 Andrea Corallo
2020-06-03 11:27 ` Florian Weimer
2020-06-03 14:14 ` Andrea Corallo
2020-06-03 14:24 ` Florian Weimer
2020-06-03 14:33 ` Adhemerval Zanella
2020-06-03 14:53 ` Szabolcs Nagy
2020-06-03 15:03 ` Szabolcs Nagy
2020-06-03 15:04 ` Adhemerval Zanella
2020-06-03 15:04 ` Florian Weimer
2020-06-03 15:18 ` Szabolcs Nagy
2020-06-03 15:24 ` Florian Weimer
2020-06-03 14:40 ` Adhemerval Zanella
2020-06-03 16:01 ` Andrea Corallo
2020-06-04 12:04 ` H.J. Lu
2020-06-04 19:48 ` Szabolcs Nagy
2020-06-04 20:03 ` H.J. Lu
2020-06-05 7:38 ` Szabolcs Nagy
2020-06-05 8:45 ` Wilco Dijkstra [this message]
2020-06-05 16:25 ` Szabolcs Nagy
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=DB8PR08MB50364FDFC5752BD36500E27D83860@DB8PR08MB5036.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=Szabolcs.Nagy@arm.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=nsz@port70.net \
/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).