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
Snapshot gcc-7-20170115 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20170115/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision
Thanks for the quick fix, and also for the 4.9.3 suggestion!
Regards,
Ashish Gupta
On Sun, Jan 15, 2017 at 1:49 PM, Jonathan Wakely wrote:
> On 15 January 2017 at 01:23, Jonathan Wakely wrote:
>> On 14 January 2017 at 12:21, Unknown wrote:
>>> Hi!
>>>
>>> I found the official GCC page for manual
I have a toy backend based on the moxie backend as a template. During its
development I found some oddities in the moxie backend that may be bugs.
1. The REGNO_OK_FOR_INDEX_P(NUM) macro in moxie.h is:
#define REGNO_OK_FOR_INDEX_P(NUM) MOXIE_FP
Since MOXIE_FP is 0, this returns false for every r
Hi,
Here's a report of a successful build and install of GCC:
$ gcc-6.3.0/config.guess
hppa2.0-unknown-linux-gnu
$ newcompiler/bin/gcc -v
Using built-in specs.
COLLECT_GCC=newcompiler/bin/gcc
COLLECT_LTO_WRAPPER=/home/aaro/gcctest/newcompiler/libexec/gcc/hppa-unknown-linux-gnu/6.3.0/lto-wrapper
On 15 January 2017 at 01:23, Jonathan Wakely wrote:
> On 14 January 2017 at 12:21, Unknown wrote:
>> Hi!
>>
>> I found the official GCC page for manuals[1].
>> But unfortunately, the libstdc++ docs for my compiler version (4.9.4)
>> cannot be accessed due to broken links on the webpage.
>>
>> These