From: Andrew Cooper <andrew.cooper3@citrix.com>
To: nicola.vetrini@gmail.com, xen-devel@lists.xenproject.org
Cc: "Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>
Subject: Re: [XEN PATCH 1/3] xen/compiler: drop alternative unreachable() definition for older GCC
Date: Wed, 13 Aug 2025 23:32:02 +0100 [thread overview]
Message-ID: <83a83cdf-91e2-4b82-89b9-b07ecdb20a3f@citrix.com> (raw)
In-Reply-To: <9215845f364527203efaea9dd1019cd1e3c1768b.1755111932.git.nicola.vetrini@bugseng.com>
On 13/08/2025 8:12 pm, nicola.vetrini@gmail.com wrote:
> From: Nicola Vetrini <nicola.vetrini@gmail.com>
>
> The GCC baseline version is 5.1, which supports __builtin_unreachable(),
> therefore the alternative definition can be dropped
>
> Signed-off-by: Nicola Vetrini <nicola.vetrini@gmail.com>
> ---
> Mentioned in https://gitlab.com/xen-project/xen/-/issues/201
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
next prev parent reply other threads:[~2025-08-13 22:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 19:12 [XEN PATCH 0/3] Drop alternative definitions for unsupported GCCs nicola.vetrini
2025-08-13 19:12 ` [XEN PATCH 1/3] xen/compiler: drop alternative unreachable() definition for older GCC nicola.vetrini
2025-08-13 22:32 ` Andrew Cooper [this message]
2025-08-13 19:12 ` [XEN PATCH 2/3] xen/macros: Drop alternative definition of BUILD_BUG_ON(_ZERO)? for old GCC nicola.vetrini
2025-08-13 22:33 ` Andrew Cooper
2025-08-14 8:07 ` Jan Beulich
2025-08-14 9:16 ` Nicola Vetrini
2025-08-13 19:12 ` [XEN PATCH 3/3] xen/efi: efibind: Drop alternative define for old GCC versions nicola.vetrini
2025-08-13 22:39 ` Andrew Cooper
2025-08-14 7:48 ` 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=83a83cdf-91e2-4b82-89b9-b07ecdb20a3f@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=nicola.vetrini@gmail.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.