From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Roberto Bagnara" <roberto.bagnara@bugseng.com>,
"Nicola Vetrini" <nicola.vetrini@bugseng.com>,
"consulting @ bugseng . com" <consulting@bugseng.com>,
"Stefano Stabellini" <sstabellini@kernel.org>
Subject: Re: [PATCH] xen: Use __auto_type
Date: Mon, 12 May 2025 13:59:21 +0200 [thread overview]
Message-ID: <548430a5-fa4a-41d1-b5ba-ba45efa90bbc@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2505051244090.3879245@ubuntu-linux-20-04-desktop>
On 05.05.2025 21:44, Stefano Stabellini wrote:
> On Mon, 5 May 2025, Andrew Cooper wrote:
>> In macros it is common to declare local variables using typeof(param) in order
>> to ensure that side effects are only evaluated once. A consequence of this is
>> double textural expansion of the parameter, which can get out of hand very
>> quickly with nested macros.
>>
>> A GCC extension, __auto_type, is now avaialble in the new toolchain baseline
>> and avoids the double textural expansion.
>
> I think this is a good change
+1
Jan
next prev parent reply other threads:[~2025-05-12 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 12:46 [PATCH] xen: Use __auto_type Andrew Cooper
2025-05-05 12:57 ` Nicola Vetrini
2025-05-05 13:00 ` Andrew Cooper
2025-05-05 19:44 ` Stefano Stabellini
2025-05-12 11:59 ` Jan Beulich [this message]
2025-05-12 12:09 ` Andrew Cooper
2025-05-12 12:41 ` Frediano Ziglio
2025-05-12 13:00 ` Jan Beulich
2025-05-12 18:25 ` Elliott Mitchell
2025-05-12 19:58 ` Nicola Vetrini
2025-05-12 23:04 ` Demi Marie Obenour
2025-05-12 23:31 ` Andrew Cooper
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=548430a5-fa4a-41d1-b5ba-ba45efa90bbc@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=consulting@bugseng.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=nicola.vetrini@bugseng.com \
--cc=roberto.bagnara@bugseng.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.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.