From: Alejandro Vallejo <alejandro.vallejo@cloud.com>
To: Andrew Cooper <andcooper@tibco.com>
Cc: Olaf Hering <olaf@aepfle.de>, Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] tools: Remove all DECLARE_* op macros in xc
Date: Mon, 6 Nov 2023 13:13:50 +0000 [thread overview]
Message-ID: <6548e690.5d0a0220.b4d80.fa60@mx.google.com> (raw)
In-Reply-To: <3620b635-0014-4def-b4c6-aadf099b0410@tibco.com>
On Mon, Nov 06, 2023 at 11:29:57AM +0000, Andrew Cooper wrote:
> On 06/11/2023 10:58 am, Olaf Hering wrote:
> > Mon, 6 Nov 2023 08:19:46 +0000 Alejandro Vallejo <alejandro.vallejo@cloud.com>:
> >
> >> + struct xen_sysctl sysctl = {0};
> > What is that zero doing here? I think a plain {} will do it as well.
>
> Indeed. It needs to be {} and not {0} to compile on some obsolete but
> still supported versions of GCC.
>
> ~Andrew
I tried to find out what you're talking about and all I could find was:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36750
I'm guessing we are already inhibiting that warning because grepping for
{0} shows a bunch of uses of this pattern both in toolstack and the
hypervisor. If this breaks something it's already broken.
Either way, sure. Let me re-generate the diff. I have strong philosophical
objections to keeping support for >10yo toolchains in detriment of >20yo
standards, but I'll just save the rant for another day.
Cheers,
Alejandro
next prev parent reply other threads:[~2023-11-06 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 8:19 [PATCH] tools: Remove all DECLARE_* op macros in xc Alejandro Vallejo
2023-11-06 10:58 ` Olaf Hering
2023-11-06 11:28 ` Alejandro Vallejo
2023-11-06 11:29 ` Andrew Cooper
2023-11-06 13:13 ` Alejandro Vallejo [this message]
2023-11-06 13:54 ` Jan Beulich
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=6548e690.5d0a0220.b4d80.fa60@mx.google.com \
--to=alejandro.vallejo@cloud.com \
--cc=andcooper@tibco.com \
--cc=olaf@aepfle.de \
--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.