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

On Mon, 18 Sep 2023, Matthew Malcomson via Gcc-patches wrote:

> 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)?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989#c13 has links to all 
the issues I filed requesting that ABIs be defined for _BitInt.

At some point all GCC architecture maintainers should probably be asked to 
try to agree _BitInt ABIs with any psABI maintainers that may exist, or, 
failing a maintained psABI, with any other implementations for the 
architecture, or, failing other maintained implementations that support 
_BitInt or might do so in future, to write down a definition of the ABI 
being used by GCC for _BitInt on that architecture along with enabling the 
support in GCC.

-- 
Joseph S. Myers
joseph@codesourcery.com

      reply	other threads:[~2023-09-18 21:31 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
2023-09-18 21:31   ` Joseph Myers [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=bd1d3765-4b5d-139-d5e4-ad55c488d98@codesourcery.com \
    --to=joseph@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=jakub@redhat.com \
    --cc=matthew.malcomson@arm.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).