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: typo and wording fixes
Date: Wed, 23 Nov 2022 14:12:27 +0000 (GMT)	[thread overview]
Message-ID: <20221123141227.16D953853D6A@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=02fee5ef63c1dd4ea4f51527717aada66caf94d3

commit 02fee5ef63c1dd4ea4f51527717aada66caf94d3
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date:   Tue Nov 22 13:36:29 2022 +0000

    morello README: typo and wording fixes

Diff:
---
 manual/README.morello | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/manual/README.morello b/manual/README.morello
index 2db20724ba..cf30eeaee5 100644
--- a/manual/README.morello
+++ b/manual/README.morello
@@ -22,16 +22,16 @@ target specific changes:
 Limitations of the morello port:
 
 - Building requires --disable-werror.
-- Profiling and --enable-profile are not supported (gperf, sprof, LD_PROFILE).
-- LD_AUDIT is not supported (symbind, PLT hooks, would require API redesign).
+- Profiling and --enable-profile are not supported (gprof, sprof, LD_PROFILE).
+- LD_AUDIT is not supported (la_symbind, PLT hooks, require new API redesign).
 - VDSO is not supported (depends on Linux work).
 - static-pie is not supported (requires start code redesign).
 - POSIX message queue async notify does not work (pointers passed via an fd).
-- Process shared robust mutexes don't work (pointers in shared memory).
+- Process shared robust mutex does not work (pointers in shared memory).
 - Purecap pldd only supports purecap ABI processes (not lp64).
 - 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.
-- Executable stacks are not supported.
+- Executable stack is not supported.
 - Internal pointer protection and pointer mangling are disabled.

                 reply	other threads:[~2022-11-23 14:12 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=20221123141227.16D953853D6A@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).