From: Jakub Jelinek <jakub@redhat.com>
To: "Andre Vieira (lists)" <andre.simoesdiasvieira@arm.com>
Cc: gcc-patches@gcc.gnu.org, Richard.Sandiford@arm.com,
kyrylo.tkachov@arm.com
Subject: Re: [PATCH 2/2] aarch64: Add support for _BitInt
Date: Wed, 28 Feb 2024 12:19:52 +0100 [thread overview]
Message-ID: <Zd8W2KZG2aJgumO1@tucnak> (raw)
In-Reply-To: <88b9a1f0-b0e2-4c61-9f5e-4cb380fa9a7c@arm.com>
On Tue, Feb 27, 2024 at 01:40:09PM +0000, Andre Vieira (lists) wrote:
> Dropped the first patch and dealt with the comments above, hopefully I
> didn't miss any this time.
>
> ----------------------------------
>
> This patch adds support for C23's _BitInt for the AArch64 port when
> compiling
> for little endianness. Big Endianness requires further target-agnostic
> support and we therefor disable it for now.
>
> gcc/ChangeLog:
>
> * config/aarch64/aarch64.cc (TARGET_C_BITINT_TYPE_INFO): Declare MACRO.
> (aarch64_bitint_type_info): New function.
> (aarch64_return_in_memory_1): Return large _BitInt's in memory.
> (aarch64_function_arg_alignment): Adapt to correctly return the ABI
> mandated alignment of _BitInt(N) where N > 128 as the alignment of
> TImode.
> (aarch64_composite_type_p): Return true for _BitInt(N), where N > 128.
>
> libgcc/ChangeLog:
>
> * config/aarch64/t-softfp (softfp_extras): Add floatbitinthf,
> floatbitintbf, floatbitinttf and fixtfbitint.
> * config/aarch64/libgcc-softfp.ver (GCC_14.0.0): Add __floatbitinthf,
> __floatbitintbf, __floatbitinttf and __fixtfbitint.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/aarch64/bitint-alignments.c: New test.
> * gcc.target/aarch64/bitint-args.c: New test.
> * gcc.target/aarch64/bitint-sizes.c: New test.
LGTM, but as this is mostly aarch64 specific, I'll defer the final ack
to Richard or Kyrylo.
Jakub
next prev parent reply other threads:[~2024-02-28 11:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 17:44 [PATCH 0/2] aarch64, bitint: Add support for _BitInt for AArch64 Little Endian Andre Vieira
2024-01-25 17:45 ` [PATCH 1/2] bitint: Use TARGET_ARRAY_MODE for large bitints where target supports it Andre Vieira
2024-02-02 15:18 ` Jakub Jelinek
2024-01-25 17:45 ` [PATCH 2/2] aarch64: Add support for _BitInt Andre Vieira
2024-01-25 19:40 ` Richard Sandiford
2024-02-02 14:46 ` Jakub Jelinek
2024-02-27 13:40 ` Andre Vieira (lists)
2024-02-28 11:19 ` Jakub Jelinek [this message]
2024-03-07 17:59 ` Richard Sandiford
2024-03-27 18:24 ` [PATCHv2 0/2] aarch64, bitint: Add support for _BitInt for AArch64 Little Endian Andre Vieira (lists)
2024-03-27 18:29 ` [PATCHv2 1/2] aarch64: Do not give ABI change diagnostics for _BitInt(N) Andre Vieira (lists)
2024-03-28 12:54 ` Richard Sandiford
2024-04-10 9:16 ` Andre Vieira (lists)
2024-04-10 10:24 ` Richard Sandiford
2024-03-27 18:31 ` [PATCHv2 2/2] aarch64: Add support for _BitInt Andre Vieira (lists)
2024-03-28 15:00 ` Richard Sandiford
2024-03-28 15:03 ` Jakub Jelinek
2024-03-28 15:21 ` Richard Sandiford
2024-04-10 9:17 ` [PATCHv3 " Andre Vieira (lists)
2024-04-10 10:27 ` Richard Sandiford
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=Zd8W2KZG2aJgumO1@tucnak \
--to=jakub@redhat.com \
--cc=Richard.Sandiford@arm.com \
--cc=andre.simoesdiasvieira@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.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 read-only IMAP folder(s) and NNTP newsgroup(s).