Re: [PATCH] Remove vr_values::extract_range_builtin.

2020-11-15 Thread Aldy Hernandez via Gcc-patches
Since Jeff says that the latest Fedora build went fine, we can safely remove the duplicated code in vr_values. Here is the original proposal rebased for latest trunk. Tested on x86-64 Linux. Pushed. commit 82b6d25d289195d41e53fc91f63325864e3e28d0 Author: Aldy Hernandez Date: Wed Oct 28 16:

Re: [PATCH] Remove vr_values::extract_range_builtin.

2020-11-14 Thread Jeff Law via Gcc-patches
On 11/14/20 1:05 PM, Aldy Hernandez wrote: > Any news on the latest snapshot? Can we remove the duplicate range > built-in code? 11-08 looks real good, best we've had since mid-sept. jeff

Re: [PATCH] Remove vr_values::extract_range_builtin.

2020-11-14 Thread Aldy Hernandez via Gcc-patches
Any news on the latest snapshot? Can we remove the duplicate range built-in code? Aldy On Thu, Nov 5, 2020, 22:43 Jeff Law wrote: > > On 11/5/20 2:40 PM, Aldy Hernandez wrote: > > I'll wait for the 11/01 snapshot to finish then. > > I'm worried that the 11/01 snapshot is going to generate so ma

Re: [PATCH] Remove vr_values::extract_range_builtin.

2020-11-05 Thread Aldy Hernandez via Gcc-patches
Ug. Well, we need to wait for something later than the 25th's snapshot since I committed the asset patch later. Aldy On Thu, Nov 5, 2020, 22:43 Jeff Law wrote: > > On 11/5/20 2:40 PM, Aldy Hernandez wrote: > > I'll wait for the 11/01 snapshot to finish then. > > I'm worried that the 11/01 s

Re: [PATCH] Remove vr_values::extract_range_builtin.

2020-11-05 Thread Jeff Law via Gcc-patches
On 11/5/20 2:40 PM, Aldy Hernandez wrote: > I'll wait for the 11/01 snapshot to finish then. I'm worried that the 11/01 snapshot is going to generate so many failures that it may not be useful.  I'm not sure what's going on, but I'm getting a ton of what appear to be codegen correctness issues.

Re: [PATCH] Remove vr_values::extract_range_builtin.

2020-11-05 Thread Aldy Hernandez via Gcc-patches
I'll wait for the 11/01 snapshot to finish then. Thanks. Aldy On Thu, Nov 5, 2020, 21:53 Jeff Law wrote: > > On 10/20/20 10:43 AM, Aldy Hernandez via Gcc-patches wrote: > > As promised. > > > > Now that we know the vr_values and ranger versions are in sync, it > > is safe to remove the vr_value

Re: [PATCH] Remove vr_values::extract_range_builtin.

2020-11-05 Thread Jeff Law via Gcc-patches
On 10/20/20 10:43 AM, Aldy Hernandez via Gcc-patches wrote: > As promised. > > Now that we know the vr_values and ranger versions are in sync, it > is safe to remove the vr_values version and just call the ranger one. > > I am holding off on pushing this for a week or two, or until Fedora gets >

Re: [PATCH] Remove vr_values::extract_range_builtin.

2020-10-20 Thread Andrew MacLeod via Gcc-patches
On 10/20/20 12:43 PM, Aldy Hernandez wrote: As promised. Now that we know the vr_values and ranger versions are in sync, it is safe to remove the vr_values version and just call the ranger one. I am holding off on pushing this for a week or two, or until Fedora gets rebuilt with the current com

[PATCH] Remove vr_values::extract_range_builtin.

2020-10-20 Thread Aldy Hernandez via Gcc-patches
As promised. Now that we know the vr_values and ranger versions are in sync, it is safe to remove the vr_values version and just call the ranger one. I am holding off on pushing this for a week or two, or until Fedora gets rebuilt with the current compiler. gcc/ChangeLog: * vr-values.h