On 08/02/2018 02:50 PM, Jeff Law wrote:
On 08/02/2018 12:23 PM, Aldy Hernandez wrote:
On 08/02/2018 02:07 PM, Jeff Law wrote:
On 08/01/2018 03:19 PM, David Malcolm wrote:
On Wed, 2018-08-01 at 15:39 -0400, Aldy Hernandez wrote:
This is actually an obvious patch, but I'm not committing it
On 08/02/2018 02:23 PM, Aldy Hernandez wrote:
On 08/02/2018 02:07 PM, Jeff Law wrote:
On 08/01/2018 03:19 PM, David Malcolm wrote:
On Wed, 2018-08-01 at 15:39 -0400, Aldy Hernandez wrote:
This is actually an obvious patch, but I'm not committing it just in
case you'd prefer another name fo
On 08/02/2018 12:23 PM, Aldy Hernandez wrote:
>
>
> On 08/02/2018 02:07 PM, Jeff Law wrote:
>> On 08/01/2018 03:19 PM, David Malcolm wrote:
>>> On Wed, 2018-08-01 at 15:39 -0400, Aldy Hernandez wrote:
This is actually an obvious patch, but I'm not committing it just in
case you'd prefer
On 08/02/2018 02:07 PM, Jeff Law wrote:
On 08/01/2018 03:19 PM, David Malcolm wrote:
On Wed, 2018-08-01 at 15:39 -0400, Aldy Hernandez wrote:
This is actually an obvious patch, but I'm not committing it just in
case you'd prefer another name for the files.
BTW, is it our policy that new gc
On 08/01/2018 03:19 PM, David Malcolm wrote:
> On Wed, 2018-08-01 at 15:39 -0400, Aldy Hernandez wrote:
>> This is actually an obvious patch, but I'm not committing it just in
>> case you'd prefer another name for the files.
>
> BTW, is it our policy that new gcc C++ source files should have a .c
On Wed, 2018-08-01 at 15:39 -0400, Aldy Hernandez wrote:
> This is actually an obvious patch, but I'm not committing it just in
> case you'd prefer another name for the files.
BTW, is it our policy that new gcc C++ source files should have a .cc
extension?
> OK pending bootstrap?
>
> Aldy
This is actually an obvious patch, but I'm not committing it just in
case you'd prefer another name for the files.
OK pending bootstrap?
Aldy
gcc/
* Makefile.in (wide-int-range.o): New.
* tree-vrp.c: Move all the wide_int_* functions to...
* wide-int-range.c: ...here.
* tree-vrp.h: Move al
