Hello all:
After have a test, "gcc version 6.0.0 20151023 (experimental) (GCC)" has
no this issue. And bug63510 can be closed. :-)
So for me, we need not spend additional time resources on it. I shall
continue to other issues in gcc or qemu. Now, I guess, my 1st priority
is to rewrite tilegx qemu
On 10/23/15 16:56, Richard Biener wrote:
> On Thu, Oct 22, 2015 at 9:46 PM, Jeff Law wrote:
>>
>> Note that the call to fold_binary from tree-ssa-sccvn.c has been removed.
>> So that hunk either needs to be removed or the change applied elsewhere.
>>
Oh, really, it uses gimple_simplify instead o
On Thu, Oct 22, 2015 at 9:46 PM, Jeff Law wrote:
> On 10/21/2015 04:31 PM, Chen Gang wrote:
>>
>> Hello all:
>>
>> It is for bug63510, which reported by another members (not me), I guess,
>> this patch should fix this bug.
>>
>> Welcome any other members' ideas, suggestions, and completions.
>
> N
On 10/21/2015 04:31 PM, Chen Gang wrote:
Hello all:
It is for bug63510, which reported by another members (not me), I guess,
this patch should fix this bug.
Welcome any other members' ideas, suggestions, and completions.
Note that the call to fold_binary from tree-ssa-sccvn.c has been
removed.
Hello all:
It is for bug63510, which reported by another members (not me), I guess,
this patch should fix this bug.
Welcome any other members' ideas, suggestions, and completions.
Thanks.
On 10/13/15 06:36, Chen Gang wrote:
> Hello all:
>
> Is this patch OK? If it still needs to do anything, p
Hello all:
Is this patch OK? If it still needs to do anything, please let me know,
I shall try.
Thanks.
On 9/1/15 21:42, Chen Gang wrote:
> On 8/31/15 19:12, Richard Biener wrote:
>> On Sat, Aug 29, 2015 at 2:57 PM, Chen Gang
>> wrote:
>>>
>>> It is about bug63510: current input_location isn't
On 8/31/15 19:12, Richard Biener wrote:
> On Sat, Aug 29, 2015 at 2:57 PM, Chen Gang
> wrote:
>>
>> It is about bug63510: current input_location isn't precise for reporting
>> warning. The correct location is gimple location of current statement.
>
> Looks ok to me. Ok if bootstrapped and tested.
On Sat, Aug 29, 2015 at 2:57 PM, Chen Gang wrote:
>
> It is about bug63510: current input_location isn't precise for reporting
> warning. The correct location is gimple location of current statement.
Looks ok to me. Ok if bootstrapped and tested.
Thanks,
Richard.
> ChangeLog:
>
> 2015-08-29 C
It is about bug63510: current input_location isn't precise for reporting
warning. The correct location is gimple location of current statement.
ChangeLog:
2015-08-29 Chen Gang
* fold-const.c (fold_overflow_warning): Call warning_at instead
of call warning.
* tree-ssa-
