public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>,
	Uros Bizjak <ubizjak@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC PATCH] Change the type of predicates to bool.
Date: Wed, 30 Jun 2021 09:00:47 -0600	[thread overview]
Message-ID: <e448a354-cab2-2023-af2b-e7e7918eafd3@gmail.com> (raw)
In-Reply-To: <CAFiYyc2sbM+RjPLgd3RWe_mpNYBDNpaT0SjtC2Z_2SOgdV-PrQ@mail.gmail.com>



On 6/30/2021 4:50 AM, Richard Biener via Gcc-patches wrote:
> On Wed, Jun 30, 2021 at 10:47 AM Uros Bizjak via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
>> This RFC patch changes the type of predicates to bool. However, some
>> of the targets (e.g. x86) use indirect functions to call the
>> predicates, so without the local change, the build fails. Putting the
>> patch through CI bots should weed out the problems, but I have no
>> infrastructure to do it myself.
> I'd say thanks for the work - note building some cc1 crosses should
> catch 99% of the fallout (just configure $target-linux/elf and make all-gcc)
Note that if he was to commit,  my tester will pick up the crosses, so 
we'll  know about any cross fallout in ~24hrs.  The "native chroot" 
tests are once a week, so if it breaks something like hppa or m68k we'd 
still know within a week.

jeff


  reply	other threads:[~2021-06-30 15:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30  8:46 Uros Bizjak
2021-06-30 10:50 ` Richard Biener
2021-06-30 15:00   ` Jeff Law [this message]
2021-07-01 13:07   ` [PATCH] " Uros Bizjak
2021-07-01 13:11     ` Richard Biener

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=e448a354-cab2-2023-af2b-e7e7918eafd3@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    --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).