On Sep 30, 2017, Alexandre Oliva wrote:
> On Aug 31, 2017, Alexandre Oliva wrote:
>> On Aug 23, 2017, Richard Biener wrote:
>>> Just separating the boilerplate changes out from the "meat" of the change
>>> into a separate patch for easier reviewing would be nice.
>> I've broken up the patch in
On Aug 31, 2017, Alexandre Oliva wrote:
> On Aug 23, 2017, Richard Biener wrote:
>> Just separating the boilerplate changes out from the "meat" of the change
>> into a separate patch for easier reviewing would be nice.
> I've broken up the patch into a patchset with 10 patches. I've already
>
On Sep 7, 2017, Joseph Myers wrote:
> On Fri, 25 Aug 2017, Alexandre Oliva wrote:
>> for gcc/ChangeLog
>>
>> * common.opt (Wa, Wl, Wp, g, gz=): Add
>> RejectNegative.
>> (gno-column-info): Remove.
>> (gcolumn-info): Drop RejectNegative.
>> (gno-): New prefix.
[...]
> OK.
Thanks, I've finally
On Fri, 25 Aug 2017, Alexandre Oliva wrote:
> for gcc/ChangeLog
>
> * common.opt (Wa, Wl, Wp, g, gz=): Add
> RejectNegative.
> (gno-column-info): Remove.
> (gcolumn-info): Drop RejectNegative.
> (gno-): New prefix.
> (gno-record-gcc-switches): Remove.
>
On Aug 23, 2017, Richard Biener wrote:
> Just separating the boilerplate changes out from the "meat" of the change
> into a separate patch for easier reviewing would be nice.
I've broken up the patch into a patchset with 10 patches. I've already
posted the one that makes -g options negatable th
On Fri, Aug 25, 2017 at 4:26 PM, Alexandre Oliva wrote:
> On Aug 23, 2017, Richard Biener wrote:
>
if they are not a problem up until here why care now?
>
>>> IIRC we do have a limit for VTA notes too, but there's a C++ testcase
>>> (g++.dg/tree-ssa/pr14703.C) that expands and inlines fibona
On Aug 23, 2017, Richard Biener wrote:
> Just curious if, for example, --with-build-config=bootstrap-lto
> --enable-languages=c
> --disable-multilib and make -j1 shows any difference in time and/or peak
> memory
> use (the interesting peak memory use is that of the WPA phase).
$ ../configure --
On Aug 23, 2017, Richard Biener wrote:
> On Wed, Aug 23, 2017 at 12:29 AM, Alexandre Oliva wrote:
>> All debug options that support negation seem to have adopted this idiom;
>> without it, the negated options end up misparsed as -g with an argument,
>> and then set_debug_level complains that "no
On Aug 23, 2017, Richard Biener wrote:
>>> if they are not a problem up until here why care now?
>> IIRC we do have a limit for VTA notes too, but there's a C++ testcase
>> (g++.dg/tree-ssa/pr14703.C) that expands and inlines fibonacci template
>> functions so deep, more than doubling the number
On Wed, Aug 23, 2017 at 12:29 AM, Alexandre Oliva wrote:
> On Aug 21, 2017, Richard Biener wrote:
>
>> +gno-statement-frontiers
>> +Common Driver RejectNegative Var(debug_nonbind_markers_p, 0) Init(2)
>> +Don't enforce progressive recommended breakpoint locations.
>> +
>> +gstatement-frontiers
>>
On Tue, Aug 22, 2017 at 10:43 PM, Alexandre Oliva wrote:
> On Aug 21, 2017, Richard Biener wrote:
>
>> On Fri, Aug 18, 2017 at 11:20 PM, Alexandre Oliva wrote:
>
>>> Besides implementing these new features, the patch contains multiple
>>> fixes for -fcompare-debug errors detected at various opti
On Aug 21, 2017, Richard Biener wrote:
> +gno-statement-frontiers
> +Common Driver RejectNegative Var(debug_nonbind_markers_p, 0) Init(2)
> +Don't enforce progressive recommended breakpoint locations.
> +
> +gstatement-frontiers
> +Common Driver RejectNegative Var(debug_nonbind_markers_p, 1)
> +E
On Aug 21, 2017, Richard Biener wrote:
> On Fri, Aug 18, 2017 at 11:20 PM, Alexandre Oliva wrote:
>> Besides implementing these new features, the patch contains multiple
>> fixes for -fcompare-debug errors detected at various optimization
>> levels, arising mainly from the introduction of begin
13 matches
Mail list logo
