From: Jakub Jelinek <jakub@redhat.com>
To: "Andre Vieira (lists)" <andre.simoesdiasvieira@arm.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [wwwdocs] Specify AArch64 BitInt support for little-endian only
Date: Tue, 7 May 2024 17:38:56 +0200 [thread overview]
Message-ID: <ZjpLELjoXYOczNY/@tucnak> (raw)
In-Reply-To: <a90a7169-890a-463d-96e0-ade4e70b2ef0@arm.com>
On Tue, May 07, 2024 at 02:12:07PM +0100, Andre Vieira (lists) wrote:
> Hey Jakub,
>
> This what ya had in mind?
Yes.
> diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
> index ca5174de991bb088f653468f77485c15a61526e6..924e045a15a78b5702a0d6997953f35c6b47efd1 100644
> --- a/htdocs/gcc-14/changes.html
> +++ b/htdocs/gcc-14/changes.html
> @@ -325,7 +325,7 @@ You may also want to check out our
> <li>Bit-precise integer types (<code>_BitInt (<i>N</i>)</code>
> and <code>unsigned _BitInt (<i>N</i>)</code>): integer types with
> a specified number of bits. These are only supported on
> - IA-32, x86-64 and AArch64 at present.</li>
> + IA-32, x86-64 and AArch64 (little-endian) at present.</li>
> <li>Structure, union and enumeration types may be defined more
> than once in the same scope with the same contents and the same
> tag; if such types are defined with the same contents and the
Jakub
prev parent reply other threads:[~2024-05-07 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 13:12 Andre Vieira (lists)
2024-05-07 15:38 ` Jakub Jelinek [this message]
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=ZjpLELjoXYOczNY/@tucnak \
--to=jakub@redhat.com \
--cc=andre.simoesdiasvieira@arm.com \
--cc=gcc-patches@gcc.gnu.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).