Re: [PATCH 00/57] Replace the Power target-specific built-in machinery

2021-05-21 Thread Bill Schmidt via Gcc-patches
On 5/20/21 4:57 PM, Segher Boessenkool wrote: Is there some (semi-)automatic way to compare the results of the old and new systems? Yes...very "semi".  There's a patch in the series that updates the information printed from -mdebug=builtin.  I use this to print the builtins generated by the

Re: [PATCH 00/57] Replace the Power target-specific built-in machinery

2021-05-20 Thread Segher Boessenkool
Hi! Just a few small things about this -- I'll reply to more of it later. On Tue, Apr 27, 2021 at 10:32:35AM -0500, Bill Schmidt via Gcc-patches wrote: > The design of the target-specific built-in function support in the > Power back end has not stood the test of time. The machinery is >

Re: [PATCH 00/57] Replace the Power target-specific built-in machinery

2021-05-11 Thread Segher Boessenkool
On Tue, May 11, 2021 at 10:57:56AM -0500, Bill Schmidt wrote: > Hi!  I'd like to ping this series.  This is a big change, so I'd like to > get it committed fairly early in stage 1.  I know you have a lot stacked > up, though. I haven't received most of this series (only the last three patches).

Re: [PATCH 00/57] Replace the Power target-specific built-in machinery

2021-05-11 Thread Bill Schmidt via Gcc-patches
Hi!  I'd like to ping this series.  This is a big change, so I'd like to get it committed fairly early in stage 1.  I know you have a lot stacked up, though. Thanks! Bill On 4/27/21 10:32 AM, Bill Schmidt wrote: The design of the target-specific built-in function support in the Power back

[PATCH 00/57] Replace the Power target-specific built-in machinery

2021-04-27 Thread Bill Schmidt via Gcc-patches
The design of the target-specific built-in function support in the Power back end has not stood the test of time. The machinery is grossly inefficient, confusing, and arcane; and adding new built-in functions is inefficient and error-prone. This patch set introduces a replacement. Because of