From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH v2 0/3] OpenRISC port
Date: Thu, 4 Oct 2018 12:48:00 +0900 [thread overview]
Message-ID: <20181004034803.18066-1-shorne@gmail.com> (raw)
Hello,
Changes Since v1:
- Document options in invoke.texi suggested by Joseph Myers
- Remove obsolete/incorrect macros suggested by Joseph Myers
- Documented or1k.c functions as requested by Jeff Law
- Add epilogue barriers suggested by Jeff Law
- Define SPECULATION_SAFE_VALUE suggested by Jeff Law
- Define and document multilib flags to enable disable instructions only
available on some CPU cores as requested on OpenRISC mailing list.
Since February this year I have been working on an OpenRISC clean room rewrite.
http://stffrdhrn.github.io/software/embedded/openrisc/2018/02/03/openrisc_gcc_rewrite.html
As per the article, the old port had issues with some of the owners signing over
FSF copyright. To get around this I discussed options with the group and in the
end I opted for a clean room rewrite.
The new code base has been written by me with lots of help from Richard
Henderson. I trust that both of us have our FSF GCC copyright's in place.
# Testing
We have been running the GCC testsuite with newlib and musl libc. The results
are good. See results published in a test build/release here:
- https://github.com/stffrdhrn/gcc/releases/tag/or1k-9.0.0-20180730
# Building
To build this requires some of the latest binutils patches submitted here:
- https://gcc.gnu.org/ml/gcc-patches/2018-08/msg01506.html
- git tree: https://github.com/stffrdhrn/binutils-gdb/tree/or1k-6
-Stafford
Stafford Horne (3):
or1k: libgcc: initial support for openrisc
or1k: testsuite: initial support for openrisc
or1k: gcc: initial support for openrisc
gcc/common/config/or1k/or1k-common.c | 41 +
gcc/config.gcc | 45 +
gcc/config/or1k/constraints.md | 55 +
gcc/config/or1k/elf.h | 42 +
gcc/config/or1k/elf.opt | 33 +
gcc/config/or1k/linux.h | 44 +
gcc/config/or1k/or1k-protos.h | 38 +
gcc/config/or1k/or1k.c | 2186 +++++++++++++++++
gcc/config/or1k/or1k.h | 392 +++
gcc/config/or1k/or1k.md | 894 +++++++
gcc/config/or1k/or1k.opt | 62 +
gcc/config/or1k/predicates.md | 84 +
gcc/config/or1k/t-or1k | 22 +
gcc/configure | 12 +
gcc/configure.ac | 12 +
gcc/doc/install.texi | 19 +
gcc/doc/invoke.texi | 62 +
gcc/doc/md.texi | 25 +
.../gcc.c-torture/execute/20101011-1.c | 3 +
gcc/testsuite/gcc.dg/20020312-2.c | 2 +
gcc/testsuite/gcc.dg/attr-alloc_size-11.c | 4 +-
gcc/testsuite/gcc.dg/builtin-apply2.c | 2 +-
gcc/testsuite/gcc.dg/nop.h | 2 +
.../torture/stackalign/builtin-apply-2.c | 2 +-
gcc/testsuite/gcc.dg/tree-ssa/20040204-1.c | 2 +-
gcc/testsuite/gcc.dg/tree-ssa/reassoc-33.c | 2 +-
gcc/testsuite/gcc.dg/tree-ssa/reassoc-34.c | 2 +-
gcc/testsuite/gcc.dg/tree-ssa/reassoc-35.c | 2 +-
gcc/testsuite/gcc.dg/tree-ssa/reassoc-36.c | 2 +-
gcc/testsuite/gcc.target/or1k/args-1.c | 19 +
gcc/testsuite/gcc.target/or1k/args-2.c | 15 +
gcc/testsuite/gcc.target/or1k/cmov-1.c | 8 +
gcc/testsuite/gcc.target/or1k/cmov-2.c | 9 +
gcc/testsuite/gcc.target/or1k/div-mul-1.c | 9 +
gcc/testsuite/gcc.target/or1k/div-mul-2.c | 9 +
gcc/testsuite/gcc.target/or1k/or1k.exp | 41 +
gcc/testsuite/gcc.target/or1k/return-1.c | 10 +
gcc/testsuite/gcc.target/or1k/return-2.c | 19 +
gcc/testsuite/gcc.target/or1k/return-3.c | 19 +
gcc/testsuite/gcc.target/or1k/return-4.c | 19 +
gcc/testsuite/gcc.target/or1k/sibcall-1.c | 18 +
gcc/testsuite/lib/target-supports.exp | 1 +
libgcc/config.host | 13 +
libgcc/config/or1k/crti.S | 33 +
libgcc/config/or1k/crtn.S | 1 +
libgcc/config/or1k/lib1funcs.S | 223 ++
libgcc/config/or1k/linux-unwind.h | 87 +
libgcc/config/or1k/sfp-machine.h | 54 +
libgcc/config/or1k/t-or1k | 22 +
49 files changed, 4713 insertions(+), 9 deletions(-)
create mode 100644 gcc/common/config/or1k/or1k-common.c
create mode 100644 gcc/config/or1k/constraints.md
create mode 100644 gcc/config/or1k/elf.h
create mode 100644 gcc/config/or1k/elf.opt
create mode 100644 gcc/config/or1k/linux.h
create mode 100644 gcc/config/or1k/or1k-protos.h
create mode 100644 gcc/config/or1k/or1k.c
create mode 100644 gcc/config/or1k/or1k.h
create mode 100644 gcc/config/or1k/or1k.md
create mode 100644 gcc/config/or1k/or1k.opt
create mode 100644 gcc/config/or1k/predicates.md
create mode 100644 gcc/config/or1k/t-or1k
create mode 100644 gcc/testsuite/gcc.target/or1k/args-1.c
create mode 100644 gcc/testsuite/gcc.target/or1k/args-2.c
create mode 100644 gcc/testsuite/gcc.target/or1k/cmov-1.c
create mode 100644 gcc/testsuite/gcc.target/or1k/cmov-2.c
create mode 100644 gcc/testsuite/gcc.target/or1k/div-mul-1.c
create mode 100644 gcc/testsuite/gcc.target/or1k/div-mul-2.c
create mode 100644 gcc/testsuite/gcc.target/or1k/or1k.exp
create mode 100644 gcc/testsuite/gcc.target/or1k/return-1.c
create mode 100644 gcc/testsuite/gcc.target/or1k/return-2.c
create mode 100644 gcc/testsuite/gcc.target/or1k/return-3.c
create mode 100644 gcc/testsuite/gcc.target/or1k/return-4.c
create mode 100644 gcc/testsuite/gcc.target/or1k/sibcall-1.c
create mode 100644 libgcc/config/or1k/crti.S
create mode 100644 libgcc/config/or1k/crtn.S
create mode 100644 libgcc/config/or1k/lib1funcs.S
create mode 100644 libgcc/config/or1k/linux-unwind.h
create mode 100644 libgcc/config/or1k/sfp-machine.h
create mode 100644 libgcc/config/or1k/t-or1k
--
2.17.1
next reply other threads:[~2018-10-04 3:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 3:48 Stafford Horne [this message]
2018-10-04 3:48 ` [OpenRISC] [PATCH v2 1/3] or1k: libgcc: initial support for openrisc Stafford Horne
2018-10-04 17:36 ` Joseph Myers
2018-10-05 3:59 ` Stafford Horne
2018-10-04 3:48 ` [OpenRISC] [PATCH v2 2/3] or1k: testsuite: " Stafford Horne
2018-10-04 19:13 ` Mike Stump
2018-10-04 3:48 ` [OpenRISC] [PATCH v2 3/3] or1k: gcc: " Stafford Horne
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=20181004034803.18066-1-shorne@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox