public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Szabolcs Nagy <nsz@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc/arm/morello/main] morello README update
Date: Fri, 18 Nov 2022 11:35:42 +0000 (GMT) [thread overview]
Message-ID: <20221118113542.05926384F494@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5b8ca6cbb1fa5a53cdb64a40541d4858295e34e3
commit 5b8ca6cbb1fa5a53cdb64a40541d4858295e34e3
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date: Thu Nov 3 15:03:47 2022 +0000
morello README update
Diff:
---
manual/README.morello | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/manual/README.morello b/manual/README.morello
index 8a2be21bd4..2db20724ba 100644
--- a/manual/README.morello
+++ b/manual/README.morello
@@ -29,7 +29,9 @@ Limitations of the morello port:
- POSIX message queue async notify does not work (pointers passed via an fd).
- Process shared robust mutexes don't work (pointers in shared memory).
- Purecap pldd only supports purecap ABI processes (not lp64).
-- malloc has significant overhead (locks and hash table lookup).
+- malloc bounds narrowing has large overhead (locks and hash table lookup).
+- malloc bounds narrowing can break code expecting page granularity protection.
+ Use GLIBC_TUNABLES=glibc.mem.cap_narrowing=0 env var as a workaround.
- string functions are not optimized.
-- Exectable stacks are not supported.
+- Executable stacks are not supported.
- Internal pointer protection and pointer mangling are disabled.
reply other threads:[~2022-11-18 11:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221118113542.05926384F494@sourceware.org \
--to=nsz@sourceware.org \
--cc=glibc-cvs@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).