From: Andrew Pinski <pinskia@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
Richard Biener <rguenther@suse.de>,
gcc-patches@gcc.gnu.org
Subject: Re: Patch ping Re: [PATCH 0/12] GCC _BitInt support [PR102989]
Date: Tue, 22 Aug 2023 15:48:27 -0700 [thread overview]
Message-ID: <CA+=Sn1mXfuh+_K=6PgdqtwE72Cg3TedyDfGqs8kvr+pKjiULoQ@mail.gmail.com> (raw)
In-Reply-To: <ZOOBkkswPQz+qk+G@tucnak>
On Mon, Aug 21, 2023 at 8:25 AM Jakub Jelinek via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Hi!
>
> On Wed, Aug 09, 2023 at 08:14:14PM +0200, Jakub Jelinek via Gcc-patches wrote:
> > Jakub Jelinek (12):
> > expr: Small optimization [PR102989]
> > lto-streamer-in: Adjust assert [PR102989]
> > phiopt: Fix phiopt ICE on vops [PR102989]
> > Middle-end _BitInt support [PR102989]
> > _BitInt lowering support [PR102989]
> > i386: Enable _BitInt on x86-64 [PR102989]
> > ubsan: _BitInt -fsanitize=undefined support [PR102989]
> > libgcc: Generated tables for _BitInt <-> _Decimal* conversions [PR102989]
> > libgcc _BitInt support [PR102989]
> > C _BitInt support [PR102989]
> > testsuite part 1 for _BitInt support [PR102989]
> > testsuite part 2 for _BitInt support [PR102989]
>
> + C _BitInt incremental fixes [PR102989]
>
> I'd like to ping this patch series.
> First 3 patches are committed, the rest awaits patch review.
>
> Joseph, could I ask now at least for an overall design review of the
> C patches (8-10,13) whether its interfaces with middle-end are ok,
> so that Richi can review the middle-end parts?
On a related note, does it make sense to add this as a C++ front-end
as an Extension too?
I noticed clang supports it for C++.
Thanks,
Andrew
>
> Thanks.
>
> Jakub
>
next prev parent reply other threads:[~2023-08-22 22:48 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 ` Andrew Pinski [this message]
2023-08-28 9:04 ` Patch ping^2 Re: [PATCH 0/12] GCC _BitInt support [PR102989] Jakub Jelinek
2023-09-18 11:39 ` Matthew Malcomson
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='CA+=Sn1mXfuh+_K=6PgdqtwE72Cg3TedyDfGqs8kvr+pKjiULoQ@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=rguenther@suse.de \
/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).