qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Roman Kiryanov" <rkir@google.com>,
	qemu-devel@nongnu.org
Cc: jansene@google.com, mett@google.com, jpcottin@google.com
Subject: Re: [PATCH 2/3] exec: avoid using C++ keywords in function parameters
Date: Wed, 19 Jun 2024 18:47:47 -0700	[thread overview]
Message-ID: <d1bb7ffd-cdb2-4753-9503-a4a57f8cfe2b@linaro.org> (raw)
In-Reply-To: <ee4149fd-890d-43c6-a7c0-0d6df63bbb2f@linaro.org>

On 6/19/24 03:22, Philippe Mathieu-Daudé wrote:
> On 19/6/24 00:45, Roman Kiryanov wrote:
>> to use the QEMU headers with a C++ compiler.
>>
>> Google-Bug-Id: 331190993
>> Change-Id: Ic4e49b9c791616bb22c973922772b0494706092c
>> Signed-off-by: Roman Kiryanov <rkir@google.com>
>> ---
>>   include/exec/memory.h | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/include/exec/memory.h b/include/exec/memory.h
>> index 1be58f694c..d7591a60d9 100644
>> --- a/include/exec/memory.h
>> +++ b/include/exec/memory.h
>> @@ -945,7 +945,7 @@ struct MemoryListener {
>>        * the current transaction.
>>        */
>>       void (*log_start)(MemoryListener *listener, MemoryRegionSection *section,
>> -                      int old, int new);
>> +                      int old_val, int new_val);
>>       /**
>>        * @log_stop:
>> @@ -964,7 +964,7 @@ struct MemoryListener {
>>        * the current transaction.
>>        */
>>       void (*log_stop)(MemoryListener *listener, MemoryRegionSection *section,
>> -                     int old, int new);
>> +                     int old_val, int new_val);
> 
> OK but please keep the implementations in sync with the prototype
> argument names:
> 
> accel/hvf/hvf-accel-ops.c:264: MemoryRegionSection *section, int old, int new)
> accel/hvf/hvf-accel-ops.c:274: MemoryRegionSection *section, int old, int new)
> accel/kvm/kvm-all.c:549:                          int old, int new)
> accel/kvm/kvm-all.c:566:                          int old, int new)
> hw/i386/xen/xen-hvm.c:430:                          int old, int new)
> hw/i386/xen/xen-hvm.c:441:                         int old, int new)
> hw/virtio/vhost.c:1070:                            int old, int new)
> hw/virtio/vhost.c:1077:                           int old, int new)
> include/exec/memory.h:948:                      int old, int new);
> include/exec/memory.h:967:                     int old, int new);
> 
> See also:
> target/arm/tcg/translate-a64.c:2161:        int new = a->imm * 3;

We're not trying to purge "new" from the entire tree, only (some) header files.


r~


  reply	other threads:[~2024-06-20  1:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18 22:45 [PATCH 2/3] exec: avoid using C++ keywords in function parameters Roman Kiryanov
2024-06-18 22:59 ` Richard Henderson
2024-06-19 10:22 ` Philippe Mathieu-Daudé
2024-06-20  1:47   ` Richard Henderson [this message]
2024-06-20 18:03 ` Paolo Bonzini

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=d1bb7ffd-cdb2-4753-9503-a4a57f8cfe2b@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=jansene@google.com \
    --cc=jpcottin@google.com \
    --cc=mett@google.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rkir@google.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 NNTP newsgroup(s).