From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Xen Devel <xen-devel@lists.xenproject.org>,
Consulting <consulting@bugseng.com>,
George Dunlap <george.dunlap@citrix.com>, Wei Liu <wl@xen.org>,
Roger Pau <roger.pau@citrix.com>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Michal Orzel <michal.orzel@amd.com>,
Julien Grall <julien@xen.org>
Subject: Re: Devise macros to encapsulate (x & -x)
Date: Wed, 22 Nov 2023 10:27:57 +0100 [thread overview]
Message-ID: <054ccbe1173f4a9ec27ca4201e6d74a2@bugseng.com> (raw)
In-Reply-To: <1799e5c8-ab8a-453f-96f0-c3b66ae446e1@suse.com>
>>
>> Jan, would you be willing to accept that other maintainers have a
>> preference for having a single MACRO even if suboptimal?
>
> I can live with that, even if I'm surprised by this perspective that
> others
> take. How can we, in reviews, tell people to make sure arguments are
> evaluated only once, when then we deliberately do otherwise in a case
> like
> the one here? The criteria of "not likely to be used in cases that have
> side effects" is an extremely fuzzy and sufficiently weak one, imo. I
> for
> one am even worried about the uses in MASK_EXTR() / MASK_INSR(), and
> would
> have considered introducing single-evaluation forms there as well.
>
>> If so, can we go ahead and commit the original patches?
>
> Well, the renaming needs to be done there anyway.
>
I can do the renaming if you don't feel particularly safe doing it on
commit. I already modified my local version to do experiments with
single evaluation anyway.
--
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)
next prev parent reply other threads:[~2023-11-22 9:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 10:17 Devise macros to encapsulate (x & -x) Nicola Vetrini
2023-11-17 11:04 ` Andrew Cooper
2023-11-17 11:15 ` Nicola Vetrini
2023-11-17 11:37 ` Jan Beulich
2023-11-18 2:46 ` Stefano Stabellini
2023-11-20 11:16 ` Julien Grall
2023-11-22 1:43 ` Stefano Stabellini
2023-11-22 8:07 ` Jan Beulich
2023-11-22 9:27 ` Nicola Vetrini [this message]
2023-11-22 21:22 ` Stefano Stabellini
2023-11-17 11:39 ` Jan Beulich
2023-11-17 16:12 ` Nicola Vetrini
2023-11-17 16:15 ` Nicola Vetrini
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=054ccbe1173f4a9ec27ca4201e6d74a2@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=consulting@bugseng.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.