From: Joseph Myers <joseph@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 13/12 v2] C _BitInt incremental fixes [PR102989]
Date: Tue, 5 Sep 2023 22:26:01 +0000 [thread overview]
Message-ID: <3d9f5c2b-2b4c-3325-4741-fa197170ab5@codesourcery.com> (raw)
In-Reply-To: <ZNUA0zC/RG/cqnB5@tucnak>
On Thu, 10 Aug 2023, Jakub Jelinek via Gcc-patches wrote:
> On Thu, Aug 10, 2023 at 12:10:07PM +0200, Jakub Jelinek via Gcc-patches wrote:
> > Here is an incremental patch which does that:
>
> Bootstrap/regtest on i686-linux (next to x86_64-linux where it went fine)
> revealed I forgot to add { target bitint } to dg-do compile lines.
>
> Here is an updated patch which does that and passes even on i686-linux.
This incremental patch is OK.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-09-05 22:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 18:14 [PATCH 0/12] GCC _BitInt support [PR102989] 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 [this message]
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
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=3d9f5c2b-2b4c-3325-4741-fa197170ab5@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.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).