qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH] mips: always include nanomips disassembler
Date: Tue, 10 Jan 2023 12:29:58 +0100	[thread overview]
Message-ID: <1fcba4cf-57b0-ceb4-61be-1708a74a7bfe@linaro.org> (raw)
In-Reply-To: <20230110084942.299460-1-pbonzini@redhat.com>

On 10/1/23 09:49, Paolo Bonzini wrote:
> Since the nanomips disassembler is not C++ code anymore, it need not
> depend on link_language == cpp.  Always include it and remove the
> CONFIG_NANOMIPS_DIS symbol.
> 
> Cc: Philippe Mathieu-Daudé <f4bug@amsat.org>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
>   disas/meson.build     | 3 +--
>   include/exec/poison.h | 1 -
>   meson.build           | 7 +------
>   target/mips/cpu.c     | 2 --
>   4 files changed, 2 insertions(+), 11 deletions(-)

Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>

> diff --git a/meson.build b/meson.build
> index 175517eafde8..bfb461d1efac 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -2478,7 +2478,7 @@ disassemblers = {
>     'x86_64' : ['CONFIG_I386_DIS'],
>     'm68k' : ['CONFIG_M68K_DIS'],
>     'microblaze' : ['CONFIG_MICROBLAZE_DIS'],
> -  'mips' : ['CONFIG_MIPS_DIS'],
> +  'mips' : [ 'CONFIG_MIPS_DIS'],

Queue to mips-next (dropping this one-space change).

>     'nios2' : ['CONFIG_NIOS2_DIS'],
>     'or1k' : ['CONFIG_OPENRISC_DIS'],
>     'ppc' : ['CONFIG_PPC_DIS'],
> @@ -2490,11 +2490,6 @@ disassemblers = {
>     'xtensa' : ['CONFIG_XTENSA_DIS'],
>     'loongarch' : ['CONFIG_LOONGARCH_DIS'],
>   }



      parent reply	other threads:[~2023-01-10 11:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10  8:49 [PATCH] mips: always include nanomips disassembler Paolo Bonzini
2023-01-10 10:44 ` Daniel P. Berrangé
2023-01-10 11:29 ` Philippe Mathieu-Daudé [this message]

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=1fcba4cf-57b0-ceb4-61be-1708a74a7bfe@linaro.org \
    --to=philmd@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).