On 11-02-15 10:22, Dominique d'Humières wrote:
Le 10 févr. 2015 à 12:42, Tom de Vries a écrit :
I think we need to understand first what's going on.
Sure, my patch was mainly to silence the failures on my working tree.
In both test-cases, on Linux with -fpic the inlining of one funct ion
> Le 10 févr. 2015 à 12:42, Tom de Vries a écrit :
>
> I think we need to understand first what's going on.
Sure, my patch was mainly to silence the failures on my working tree.
> In both test-cases, on Linux with -fpic the inlining of one function into the
> other is not done, because we can
Tom,
At -m32 on x86_64-apple-darwin14, the failing test case executes...
% /sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/gcc/xgcc
-B/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/gcc/
/sw/src/fink.build/gcc50-5.0.0-1000/gcc-5-20150209/gcc/testsuite/gcc.dg/uninit-19.c
-fno-diagnostics
On 09-02-15 20:01, Dominique d'Humières wrote:
Le 9 févr. 2015 à 19:10, Tom de Vries mailto:tom_devr...@mentor.com>> a écrit :
On 09-02-15 18:23, Dominique Dhumieres wrote:
Tom,
After these changes I have the following regressions on
x86_64-apple-darwin1[04]*:
FAIL: gcc.dg/uninit-19.c (tes
Also, aren't we pretty much the only target to default to PIC? So if
the 'target' and 'nonpic' testing is failing when used in the context
of dg-warning, wouldn't that appear functional on the nonpic targets?
That is, since the nonpic test is to check for __PIC__, if that fails
in dg-warning, woul
This appears to be the first instance where 'target' and 'nonpic' have
been used in a dg-warning.
On Mon, Feb 9, 2015 at 2:40 PM, Dominique d'Humières wrote:
>
>> Le 9 févr. 2015 à 20:01, Dominique d'Humières a écrit :
>>
>>
>>> Le 9 févr. 2015 à 19:10, Tom de Vries a écrit :
>>>
>>> On 09-02-1
> Le 9 févr. 2015 à 20:01, Dominique d'Humières a écrit :
>
>
>> Le 9 févr. 2015 à 19:10, Tom de Vries a écrit :
>>
>> On 09-02-15 18:23, Dominique Dhumieres wrote:
>>> Tom,
>>>
>>> After these changes I have the following regressions on
>>> x86_64-apple-darwin1[04]*:
>>>
>>> FAIL: gcc.dg/
On 09-02-15 18:23, Dominique Dhumieres wrote:
Tom,
After these changes I have the following regressions on
x86_64-apple-darwin1[04]*:
FAIL: gcc.dg/uninit-19.c (test for warnings, line 22)
FAIL: gcc.dg/uninit-19.c (test for excess errors)
FAIL: gcc.dg/graphite/scop-19.c scan-tree-dump-times gr
Tom,
After these changes I have the following regressions on
x86_64-apple-darwin1[04]*:
FAIL: gcc.dg/uninit-19.c (test for warnings, line 22)
FAIL: gcc.dg/uninit-19.c (test for excess errors)
FAIL: gcc.dg/graphite/scop-19.c scan-tree-dump-times graphite "number of SCoPs:
0" 1
I can prepare an
On Wed, Feb 4, 2015 at 10:45 AM, Tom de Vries wrote:
> Hi,
>
> I've observed a FAILURE for gcc.dg/graphite/scop-19.c with fpic:
> ...
> FAIL: gcc.dg/graphite/scop-19.c scan-tree-dump-times graphite "number of
> SCoPs: 0" 2
> ...
>
> In the nonpic case, d_growable_string_resize is inlined into
> d_
Hi,
I've observed a FAILURE for gcc.dg/graphite/scop-19.c with fpic:
...
FAIL: gcc.dg/graphite/scop-19.c scan-tree-dump-times graphite "number of SCoPs:
0" 2
...
In the nonpic case, d_growable_string_resize is inlined into
d_growable_string_append_buffer, and we have 2 functions with a loop, w
11 matches
Mail list logo