From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH 0/2] OpenRISC Remove 64-bit support to fit 32-bit hosts (PR 25184)
Date: Wed, 11 Dec 2019 06:49:04 +0900 [thread overview]
Message-ID: <20191210214906.21465-1-shorne@gmail.com> (raw)
The issue was reported by Rich Felker, OpenRISC gas fails to calculate negative
offsets when running on 32-bit hosts. I traced this back to having 64-bit
address space support in the CPU definitions. It seems we could fix this by
either adding some fixes for cgen to support this case or by adding some custom
C to do the jump offset calculations.
However, realizing that OpenRISC 64-bit support is not tested, not used and no
hardware or simulators exist I am deciding removing it is easiest.
Stafford Horne (2):
or1k: Remove 64-bit support, it's not used and it breaks 32-bit hosts
or1k: Regnerate opcode files after removing 64-bit support
cpu/or1k.cpu | 35 +-
cpu/or1kcommon.cpu | 14 -
cpu/or1korfpx.cpu | 64 --
opcodes/or1k-asm.c | 9 -
opcodes/or1k-desc.c | 1811 +++++++++++++++++++----------------------
opcodes/or1k-desc.h | 332 ++++----
opcodes/or1k-dis.c | 9 -
opcodes/or1k-ibld.c | 60 +-
opcodes/or1k-opc.c | 152 ----
opcodes/or1k-opc.h | 28 +-
opcodes/or1k-opinst.c | 428 +++++-----
11 files changed, 1185 insertions(+), 1757 deletions(-)
--
2.21.0
next reply other threads:[~2019-12-10 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 21:49 Stafford Horne [this message]
2019-12-10 21:49 ` [OpenRISC] [PATCH 1/2] or1k: Remove 64-bit support, it's not used and it breaks 32-bit hosts Stafford Horne
2019-12-10 21:49 ` [OpenRISC] [PATCH 2/2] or1k: Regnerate opcode files after removing 64-bit support Stafford Horne
2019-12-11 11:44 ` 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=20191210214906.21465-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 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.