From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org,
"Pavel Dovgalyuk" <pavel.dovgaluk@ispras.ru>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Stefan Berger" <stefanb@linux.vnet.ibm.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Juan Quintela" <quintela@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [PATCH v3 2/3] qapi: Do not generate empty enum
Date: Thu, 16 Mar 2023 13:54:42 +0000 [thread overview]
Message-ID: <ZBMfosr0JDyfjhqs@redhat.com> (raw)
In-Reply-To: <87cz58ubcn.fsf@pond.sub.org>
On Thu, Mar 16, 2023 at 01:31:04PM +0100, Markus Armbruster wrote:
> Philippe Mathieu-Daudé <philmd@linaro.org> writes:
>
> > Per the C++ standard, empty enum are ill-formed. Do not generate
> > them in order to avoid:
> >
> > In file included from qga/qga-qapi-emit-events.c:14:
> > qga/qga-qapi-emit-events.h:20:1: error: empty enum is invalid
> > 20 | } qga_QAPIEvent;
> > | ^
> >
> > Reported-by: Markus Armbruster <armbru@redhat.com>
> > Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>
> Two failures in "make check-qapi-schema" (which is run by "make check"):
>
> 1. Positive test case qapi-schema-test
>
> --- /work/armbru/qemu/bld-x86/../tests/qapi-schema/qapi-schema-test.out
> +++
> @@ -19,7 +19,6 @@
> member enum2: EnumOne optional=True
> member enum3: EnumOne optional=False
> member enum4: EnumOne optional=True
> -enum MyEnum
> object Empty1
> object Empty2
> base Empty1
>
> You forgot to update expected test output. No big deal.
>
> 2. Negative test case union-empty
>
> --- /work/armbru/qemu/bld-x86/../tests/qapi-schema/union-empty.err
> +++
> @@ -1,2 +1,2 @@
> -union-empty.json: In union 'Union':
> -union-empty.json:4: union has no branches
> +union-empty.json: In struct 'Base':
> +union-empty.json:3: member 'type' uses unknown type 'Empty'
> stderr:
> qapi-schema-test FAIL
> union-empty FAIL
>
> The error message regresses.
>
> I can see two ways to fix this:
>
> (A) You can't just drop empty enumeration types on the floor. To not
> generate code for them, you need to skip them wherever we
> generate code for enumeration types.
>
> (B) Outlaw empty enumeration types.
>
> I recommend to give (B) a try, it's likely simpler.
Possible trap-door with (B), if we have any enums where *every*
member is conditionalized on a CONFIG_XXX rule, there might be
certain build scenarios where an enum suddenly becomes empty.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-03-16 13:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 11:28 [PATCH v3 0/3] qapi: Simplify enum generation Philippe Mathieu-Daudé
2023-03-15 11:28 ` [PATCH v3 1/3] scripts/git.orderfile: Display QAPI script changes before schema ones Philippe Mathieu-Daudé
2023-03-15 15:14 ` Philippe Mathieu-Daudé
2023-03-15 20:30 ` Juan Quintela
2023-03-15 11:28 ` [PATCH v3 2/3] qapi: Do not generate empty enum Philippe Mathieu-Daudé
2023-03-15 15:02 ` Richard Henderson
2023-03-16 12:31 ` Markus Armbruster
2023-03-16 13:54 ` Daniel P. Berrangé [this message]
2023-03-16 14:39 ` Juan Quintela
2023-03-16 14:42 ` Daniel P. Berrangé
2023-03-16 14:57 ` Markus Armbruster
2023-03-21 14:31 ` Philippe Mathieu-Daudé
2023-03-21 15:19 ` Daniel P. Berrangé
2023-03-21 21:43 ` Eric Blake
2023-03-22 5:45 ` Markus Armbruster
2023-03-21 14:48 ` Philippe Mathieu-Daudé
2023-03-21 19:00 ` Markus Armbruster
2023-03-15 11:28 ` [PATCH v3 3/3] qapi: Generate enum count as definition Philippe Mathieu-Daudé
2023-03-15 19:58 ` Dr. David Alan Gilbert
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=ZBMfosr0JDyfjhqs@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=michael.roth@amd.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanb@linux.vnet.ibm.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).