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: Provide documentation about the morello port.
Date: Wed, 26 Oct 2022 15:22:21 +0000 (GMT)	[thread overview]
Message-ID: <20221026152221.E64E33838A8D@sourceware.org> (raw)

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

commit c01ec3989d67ecb3c25d90fe54cd455798111145
Author: Szabolcs Nagy <szabolcs.nagy@arm.com>
Date:   Wed Oct 19 16:08:54 2022 +0100

    morello: Provide documentation about the morello port.

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

diff --git a/manual/README.morello b/manual/README.morello
new file mode 100644
index 0000000000..8a2be21bd4
--- /dev/null
+++ b/manual/README.morello
@@ -0,0 +1,35 @@
+Morello glibc port
+==================
+
+Morello is a prototype security architecture, led by Arm, based on CHERI.
+https://www.morello-project.org/
+https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/
+
+Toolchain components of the morello port are maintained in upstream branches.
+The morello port is implemented as an ABI variant of the aarch64 port that is
+also called the purecap ABI. Morello specific ABI documents are at:
+https://github.com/ARM-software/abi-aa
+https://git.morello-project.org/morello/kernel/linux/-/wikis/home
+
+Areas with significant morello or CHERI specific changes outside the usual
+target specific changes:
+
+- Early start code including ELF entry and auxv,
+- Dynamic linker and relocation processing,
+- malloc with narrow capability support,
+- printf %#p to pretty print capabilities.
+
+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).
+- 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).
+- Purecap pldd only supports purecap ABI processes (not lp64).
+- malloc has significant overhead (locks and hash table lookup).
+- string functions are not optimized.
+- Exectable stacks are not supported.
+- Internal pointer protection and pointer mangling are disabled.

             reply	other threads:[~2022-10-26 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 15:22 Szabolcs Nagy [this message]
2022-10-27 14:00 Szabolcs Nagy
2022-11-23 14:50 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=20221026152221.E64E33838A8D@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).