On Sun, Jan 15, 2017 at 4:15 PM, Andrew Pinski wrote:
> On Sun, Jan 15, 2017 at 4:09 PM, kugan
> wrote:
>>
>>
>> On 15/01/17 15:57, Andrew Pinski wrote:
>>>
>>> Just this is just an FYI until I reduce the testcases but 5 benchmarks
>>> in SPEC CPU 2006 with fortran code is causing an ICE on
>>> a
On Sun, Jan 15, 2017 at 4:09 PM, kugan
wrote:
>
>
> On 15/01/17 15:57, Andrew Pinski wrote:
>>
>> Just this is just an FYI until I reduce the testcases but 5 benchmarks
>> in SPEC CPU 2006 with fortran code is causing an ICE on
>> aarch64-linux-gnu with -Ofast -flto -mcpu=thunderx2t99
>> -fno-aggr
On 15/01/17 15:57, Andrew Pinski wrote:
Just this is just an FYI until I reduce the testcases but 5 benchmarks
in SPEC CPU 2006 with fortran code is causing an ICE on
aarch64-linux-gnu with -Ofast -flto -mcpu=thunderx2t99
-fno-aggressive-loop-optimizations -funroll-loops:
lto1: internal compile
Just this is just an FYI until I reduce the testcases but 5 benchmarks
in SPEC CPU 2006 with fortran code is causing an ICE on
aarch64-linux-gnu with -Ofast -flto -mcpu=thunderx2t99
-fno-aggressive-loop-optimizations -funroll-loops:
lto1: internal compiler error: in ipa_get_type, at ipa-prop.h:448
