From: "Jose E. Marchesi" <jemarch@gnu.org>
To: "Frank Ch. Eigler via Cgen" <cgen@sourceware.org>
Cc: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Subject: Re: [PATCH] desc-cpu.scm: support passing the instruction endianness to cgen_cpu_open
Date: Fri, 29 May 2020 16:52:04 +0200 [thread overview]
Message-ID: <87v9kekd4b.fsf@gnu.org> (raw)
In-Reply-To: <87zha1lnpw.fsf@gnu.org> (Jose E. Marchesi's message of "Thu, 21 May 2020 10:02:51 +0200")
> The accompanying patch for opcodes will be sent to
> binutils@sourceware.org today. This CGEN patch will have to be applied
> first though.
>
> OK for master?
Sure, and it seems to have been anticipated.
Thanks. I will push once the binutils stuff is also ready... found a
complication.
Ok I think I got the binutils side nailed. Will post the patches to
binutils@sourceware once regression testing finishes running, later
today.
After the binutils part is approved I will push the following (fixed)
version of the CGEN patch, to master:
commit b684299385722879c5658f99cdbe0c63a8bc7362 (HEAD -> jemarch/cgen-insn-endian, malditobastardo/jemarch/cgen-insn-endian)
Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Date: Fri May 29 16:03:48 2020 +0200
desc-cpu.scm: support passing the instruction endianness to cgen_cpu_open
2020-05-29 Jose E. Marchesi <jemarch@gnu.org>
* desc-cpu.scm (/gen-cpu-open): Support passing the instruction
endianness to cgen_cpu_open.
diff --git a/ChangeLog b/ChangeLog
index e554fa2..93eafe4 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2020-05-29 Jose E. Marchesi <jemarch@gnu.org>
+
+ * desc-cpu.scm (/gen-cpu-open): Support passing the instruction
+ endianness to cgen_cpu_open.
+
2020-05-21 Alan Modra <amodra@gmail.com>
* desc-cpu.scm (@arch@_cgen_cpu_close): Free without first
diff --git a/desc-cpu.scm b/desc-cpu.scm
index 5bf5bc7..34f5d5c 100644
--- a/desc-cpu.scm
+++ b/desc-cpu.scm
@@ -788,6 +788,7 @@ static void
CGEN_CPU_OPEN_MACHS: bitmap of values in enum mach_attr
CGEN_CPU_OPEN_BFDMACH: specify 1 mach using bfd name
CGEN_CPU_OPEN_ENDIAN: specify endian choice
+ CGEN_CPU_OPEN_INSN_ENDIAN: specify instruction endian choice
CGEN_CPU_OPEN_END: terminates arguments
??? Simultaneous multiple isas might not make sense, but it's not (yet)
@@ -801,6 +802,7 @@ CGEN_CPU_DESC
CGEN_BITSET *isas = 0; /* 0 = \"unspecified\" */
unsigned int machs = 0; /* 0 = \"unspecified\" */
enum cgen_endian endian = CGEN_ENDIAN_UNKNOWN;
+ enum cgen_endian insn_endian = CGEN_ENDIAN_UNKNOWN;
va_list ap;
if (! init_p)
@@ -835,6 +837,9 @@ CGEN_CPU_DESC
case CGEN_CPU_OPEN_ENDIAN :
endian = va_arg (ap, enum cgen_endian);
break;
+ case CGEN_CPU_OPEN_INSN_ENDIAN :
+ insn_endian = va_arg (ap, enum cgen_endian);
+ break;
default :
opcodes_error_handler
(/* xgettext:c-format */
@@ -864,11 +869,8 @@ CGEN_CPU_DESC
cd->isas = cgen_bitset_copy (isas);
cd->machs = machs;
cd->endian = endian;
- /* FIXME: for the sparc case we can determine insn-endianness statically.
- The worry here is where both data and insn endian can be independently
- chosen, in which case this function will need another argument.
- Actually, will want to allow for more arguments in the future anyway. */
- cd->insn_endian = endian;
+ cd->insn_endian
+ = (insn_endian == CGEN_ENDIAN_UNKNOWN ? endian : insn_endian);
/* Table (re)builder. */
cd->rebuild_tables = @arch@_cgen_rebuild_tables;
next prev parent reply other threads:[~2020-05-29 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 12:45 Jose E. Marchesi
2020-05-20 7:28 ` Andrew Burgess
2020-05-21 1:26 ` Frank Ch. Eigler
2020-05-21 8:02 ` Jose E. Marchesi
2020-05-29 14:52 ` Jose E. Marchesi [this message]
2020-06-04 13:58 ` Jose E. Marchesi
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=87v9kekd4b.fsf@gnu.org \
--to=jemarch@gnu.org \
--cc=cgen@sourceware.org \
--cc=jose.marchesi@oracle.com \
/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).