public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthew Malcomson <matthew.malcomson@arm.com>
To: Jakub Jelinek <jakub@redhat.com>,
	Richard Biener <rguenther@suse.de>,
	"Joseph S. Myers" <joseph@codesourcery.com>,
	Uros Bizjak <ubizjak@gmail.com>,
	hjl.tools@gmail.com
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 0/12] GCC _BitInt support [PR102989]
Date: Mon, 18 Sep 2023 12:39:41 +0100	[thread overview]
Message-ID: <bbf278c7-3b97-6bba-d1b0-e6608ca10b5c@arm.com> (raw)
In-Reply-To: <ZNPXdkEC7m01caOV@tucnak>

On 8/9/23 19:14, Jakub Jelinek via Gcc-patches wrote:

> It is enabled only on targets which have agreed on processor specific
> ABI how to lay those out or pass as function arguments/return values,
> which currently is just x86-64 I believe, would be nice if target maintainers
> helped to get agreement on psABI changes and GCC 14 could enable it on far
> more architectures than just one.
>
Hello,

Do you know of any other architectures in the process of defining a 
psABI for _BitInt (or for that matter having defined an ABI between then 
and now)?

We're currently working on completing the ABI for AArch64 and AArch32 
hoping that it could unblock the enablement for those arches.
We'd like to know about the potential clashes with other ABI's w.r.t. 
user-visible behaviour as part of the decision making.

I'd not found any other defined ABI's online, but thought it worth 
asking in case I just missed it.

Thanks,

Matthew


  parent reply	other threads:[~2023-09-18 11:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 18:14 Jakub Jelinek
2023-08-09 21:17 ` Joseph Myers
2023-08-10  6:55   ` Richard Biener
2023-08-10  7:12     ` Jakub Jelinek
2023-08-10  7:26       ` Andrew Pinski
2023-08-10 10:10   ` [PATCH 13/12] C _BitInt incremental fixes [PR102989] Jakub Jelinek
2023-08-10 15:22     ` [PATCH 13/12 v2] " Jakub Jelinek
2023-09-05 22:26       ` Joseph Myers
2023-08-21 15:24 ` Patch ping Re: [PATCH 0/12] GCC _BitInt support [PR102989] Jakub Jelinek
2023-08-21 17:32   ` Joseph Myers
2023-08-22 11:28     ` [PATCH 14/12] libgcc _BitInt helper documentation [PR102989] Jakub Jelinek
2023-09-01 21:32       ` Joseph Myers
2023-09-02 11:41         ` Jakub Jelinek
2023-08-22 22:48   ` Patch ping Re: [PATCH 0/12] GCC _BitInt support [PR102989] Andrew Pinski
2023-08-28  9:04   ` Patch ping^2 " Jakub Jelinek
2023-09-18 11:39 ` Matthew Malcomson [this message]
2023-09-18 21:31   ` Joseph Myers

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=bbf278c7-3b97-6bba-d1b0-e6608ca10b5c@arm.com \
    --to=matthew.malcomson@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=rguenther@suse.de \
    --cc=ubizjak@gmail.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).