From: Bill Schmidt <wschmidt@linux.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: David Edelsohn <dje.gcc@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] rs6000: __builtin_darn[_raw] should be in [power9-64] (PR103624)
Date: Wed, 15 Dec 2021 14:13:53 -0600 [thread overview]
Message-ID: <ec657758-e6ea-3b3e-0639-02c1b64db33e@linux.ibm.com> (raw)
In-Reply-To: <20211215184139.GN614@gate.crashing.org>
On 12/15/21 12:41 PM, Segher Boessenkool wrote:
> On Wed, Dec 15, 2021 at 08:00:02AM -0600, Bill Schmidt wrote:
>>> No, all builtins should work in either mode, and always return long.
>>> If the patterns are broken, the *patterns* should be fixed :-)
>> OK, thanks! This is much clearer now.
>>
>> I've opened an internal issue about the deficiencies of the darn patterns and
>> their associated built-ins. In response to PR103624, I would like to start
>> with the existing patch to ensure the new support mirrors what we had before,
>> so we have that as a baseline. We can then move on to fixing the larger
>> set of problems. Is that a reasonable plan?
> It is much more work than doing it correct in the first place.
>
> I'll do the RTL side, if you want?
Sure, go ahead.
Bill
>
>
> Segher
prev parent reply other threads:[~2021-12-15 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 15:48 Bill Schmidt
2021-12-13 16:30 ` David Edelsohn
2021-12-13 16:54 ` Segher Boessenkool
2021-12-13 20:37 ` Bill Schmidt
2021-12-14 0:22 ` Segher Boessenkool
2021-12-14 13:32 ` Bill Schmidt
2021-12-14 15:17 ` Bill Schmidt
2021-12-15 2:23 ` Segher Boessenkool
2021-12-15 14:00 ` Bill Schmidt
2021-12-15 18:41 ` Segher Boessenkool
2021-12-15 20:13 ` Bill Schmidt [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=ec657758-e6ea-3b3e-0639-02c1b64db33e@linux.ibm.com \
--to=wschmidt@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
/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).