From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH v5 13/13] Documentation for OpenRISC port
Date: Wed, 5 Jan 2022 06:38:41 +0900 [thread overview]
Message-ID: <YdS+YS2v58Oz7wL4@antec> (raw)
In-Reply-To: <b4207a34-da46-1464-dec2-70c3a39e969d@linaro.org>
On Tue, Jan 04, 2022 at 09:28:12AM -0300, Adhemerval Zanella wrote:
>
>
> On 04/01/2022 00:14, Stafford Horne via Libc-alpha wrote:
> > OpenRISC architecture specification:
> >
> > https://raw.githubusercontent.com/openrisc/doc/master/openrisc-arch-1.3-rev1.pdf
> >
> > Currently the port as of the 2022-01-03 rebasing there are no known
> > architecture specific test failures.
> >
> > Writing credits for the port are:
> >
> > Stafford Horne <shorne@gmail.com>
> > Christian Svensson <blue@cmd.nu>
>
> LGTM, thanks.
>
> Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Thank you.
> > ---
> > NEWS | 9 +++++++++
> > README | 1 +
> > 2 files changed, 10 insertions(+)
> >
> > diff --git a/NEWS b/NEWS
> > index 9da2a740ec..1b7a64d654 100644
> > --- a/NEWS
> > +++ b/NEWS
> > @@ -106,6 +106,15 @@ Major new features:
> > can use it to efficiently locate unwinding information for a code
> > address.
> >
> > +* Support for OpenRISC running on Linux has been added. This port requires
> > + as least binutils 2.35, GCC 11, and Linux 5.4. Currently only soft-float
> > + ABI is supported:
> > +
> > + - or1k-linux-gnu
> > +
> > + The OpenRISC ABI is 32-bit big-endian and uses 64-bit time (y2038 safe) and
> > + 64-bit file offsets (LFS default).
> > +
> > Deprecated and removed features, and other changes affecting compatibility:
> >
> > * On x86-64, the LD_PREFER_MAP_32BIT_EXEC environment variable support
> > diff --git a/README b/README
> > index d0f0edb393..3d5a78ccff 100644
> > --- a/README
> > +++ b/README
> > @@ -35,6 +35,7 @@ The GNU C Library supports these configurations for using Linux kernels:
> > microblaze*-*-linux-gnu
> > mips-*-linux-gnu
> > mips64-*-linux-gnu
> > + or1k-*-linux-gnu
> > powerpc-*-linux-gnu Hardware or software floating point, BE only.
> > powerpc64*-*-linux-gnu Big-endian and little-endian.
> > s390-*-linux-gnu
next prev parent reply other threads:[~2022-01-04 21:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 3:14 [OpenRISC] [PATCH v5 00/13] Glibc OpenRISC port Stafford Horne
2022-01-04 3:14 ` [OpenRISC] [PATCH v5 01/13] elf: Add reloc for OpenRISC Stafford Horne
2022-01-04 3:14 ` [OpenRISC] [PATCH v5 02/13] linux/syscalls: Add or1k_atomic syscall " Stafford Horne
2022-01-04 3:14 ` [OpenRISC] [PATCH v5 03/13] or1k: ABI Implementation Stafford Horne
2022-01-04 3:14 ` [OpenRISC] [PATCH v5 04/13] or1k: startup and dynamic linking code Stafford Horne
2022-01-04 3:14 ` [OpenRISC] [PATCH v5 05/13] or1k: Thread Local Storage support Stafford Horne
2022-01-04 3:14 ` [OpenRISC] [PATCH v5 06/13] or1k: Atomics and Locking primitives Stafford Horne
2022-01-04 3:14 ` [OpenRISC] [PATCH v5 07/13] or1k: math soft float support Stafford Horne
2022-01-04 3:14 ` [OpenRISC] [PATCH v5 08/13] or1k: Linux Syscall Interface Stafford Horne
2022-01-04 3:14 ` [OpenRISC] [PATCH v5 09/13] or1k: Linux ABI Stafford Horne
2022-01-04 3:14 ` [OpenRISC] [PATCH v5 10/13] or1k: ABI lists Stafford Horne
2022-01-04 12:27 ` Adhemerval Zanella
2022-01-04 21:37 ` Stafford Horne
2022-01-04 3:14 ` [OpenRISC] [PATCH v5 11/13] or1k: Build Infrastructure Stafford Horne
2022-01-04 3:14 ` [OpenRISC] [PATCH v5 12/13] build-many-glibcs.py: add OpenRISC support Stafford Horne
2022-01-04 3:14 ` [OpenRISC] [PATCH v5 13/13] Documentation for OpenRISC port Stafford Horne
2022-01-04 12:28 ` Adhemerval Zanella
2022-01-04 21:38 ` Stafford Horne [this message]
2022-01-04 12:34 ` [OpenRISC] [PATCH v5 00/13] Glibc " Adhemerval Zanella
2022-01-04 21:36 ` Stafford Horne
2022-01-05 21:34 ` [OpenRISC] [PATCH v5 00/13] Glibc OpenRISC port - PUSHED Stafford Horne
2022-01-24 13:23 ` [OpenRISC] [PATCH v5 00/13] Glibc OpenRISC port Florian Weimer
2022-01-24 13:54 ` Adhemerval Zanella
2022-01-25 1:19 ` Stafford Horne
2022-01-25 17:07 ` Adhemerval Zanella
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=YdS+YS2v58Oz7wL4@antec \
--to=shorne@gmail.com \
--cc=openrisc@lists.librecores.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.