From: Luis Machado <luis.machado@arm.com>
To: binutils@sourceware.org
Subject: Re: [PATCH] Move TILE-Gx files to TARGET64_LIBOPCODES_CFILES
Date: Tue, 3 May 2022 22:51:53 +0100 [thread overview]
Message-ID: <8ae6b4ec-264c-2435-eac4-a7b96a3422c2@arm.com> (raw)
In-Reply-To: <20220503214654.908846-1-luis.machado@arm.com>
On 5/3/22 22:46, Luis Machado via Binutils wrote:
> TILE-Gx is a 64-bit core, so we should include those files in the
> TARGET64_LIBOPCODES_CFILES as opposed to TARGET32_LIBOPCODES_CFILES.
> ---
> opcodes/Makefile.am | 6 +++---
> opcodes/Makefile.in | 6 +++---
> 2 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/opcodes/Makefile.am b/opcodes/Makefile.am
> index afd19fa7785..10ea3368d7f 100644
> --- a/opcodes/Makefile.am
> +++ b/opcodes/Makefile.am
> @@ -115,7 +115,9 @@ TARGET64_LIBOPCODES_CFILES = \
> mmix-opc.c \
> nfp-dis.c \
> riscv-dis.c \
> - riscv-opc.c
> + riscv-opc.c \
> + tilegx-dis.c \
> + tilegx-opc.c
>
> TARGET32_LIBOPCODES_CFILES = \
> arc-dis.c \
> @@ -252,8 +254,6 @@ TARGET32_LIBOPCODES_CFILES = \
> tic54x-dis.c \
> tic54x-opc.c \
> tic6x-dis.c \
> - tilegx-dis.c \
> - tilegx-opc.c \
> tilepro-dis.c \
> tilepro-opc.c \
> v850-dis.c \
> diff --git a/opcodes/Makefile.in b/opcodes/Makefile.in
> index 3ab8bfb0548..b8545a0fa82 100644
> --- a/opcodes/Makefile.in
> +++ b/opcodes/Makefile.in
> @@ -507,7 +507,9 @@ TARGET64_LIBOPCODES_CFILES = \
> mmix-opc.c \
> nfp-dis.c \
> riscv-dis.c \
> - riscv-opc.c
> + riscv-opc.c \
> + tilegx-dis.c \
> + tilegx-opc.c
>
> TARGET32_LIBOPCODES_CFILES = \
> arc-dis.c \
> @@ -644,8 +646,6 @@ TARGET32_LIBOPCODES_CFILES = \
> tic54x-dis.c \
> tic54x-opc.c \
> tic6x-dis.c \
> - tilegx-dis.c \
> - tilegx-opc.c \
> tilepro-dis.c \
> tilepro-opc.c \
> v850-dis.c \
FTR, gdb-side patch touching TILE-Gx sent here:
https://sourceware.org/pipermail/gdb-patches/2022-May/188650.html
next prev parent reply other threads:[~2022-05-03 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 21:46 Luis Machado
2022-05-03 21:51 ` Luis Machado [this message]
2022-05-04 4:40 ` Alan Modra
2022-05-05 9:04 ` Luis Machado
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=8ae6b4ec-264c-2435-eac4-a7b96a3422c2@arm.com \
--to=luis.machado@arm.com \
--cc=binutils@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).