From: "Jose E. Marchesi" <jemarch@gnu.org>
To: "Frank Ch. Eigler via Cgen" <cgen@sourceware.org>
Cc: "Jose E. Marchesi" <jose.marchesi@oracle.com>,
"Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: [PATCH] desc-cpu.scm: support passing the instruction endianness to cgen_cpu_open
Date: Thu, 21 May 2020 10:02:51 +0200 [thread overview]
Message-ID: <87zha1lnpw.fsf@gnu.org> (raw)
In-Reply-To: <20200521012617.GD21615@redhat.com> (Frank Ch. Eigler via Cgen's message of "Wed, 20 May 2020 21:26:17 -0400")
> 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.
(Actually, the whole handling of endianness in both CGEN and binutils is
a mess. Trying to get some sense of it.)
next prev parent reply other threads:[~2020-05-21 8:02 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 [this message]
2020-05-29 14:52 ` Jose E. Marchesi
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=87zha1lnpw.fsf@gnu.org \
--to=jemarch@gnu.org \
--cc=cgen@sourceware.org \
--cc=fche@redhat.com \
--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).