On Tue, 2016-05-31 at 13:38 +0200, Uros Bizjak wrote:
> On Mon, May 30, 2016 at 12:09 AM, J. Mayer wrote:
> >
> > Hello,
> >
> > On Sun, 2016-05-29 at 21:12 +0200, Uros Bizjak wrote:
> > >
> > > Hello!
> > >
> > > >
> > > >
> > > > When trying to compile using -march=native on a VIA nano CPU
On Mon, May 30, 2016 at 12:09 AM, J. Mayer wrote:
> Hello,
>
> On Sun, 2016-05-29 at 21:12 +0200, Uros Bizjak wrote:
>> Hello!
>>
>> >
>> > When trying to compile using -march=native on a VIA nano CPU, gcc
>> > selects "-march=core2" "-mtune=i386" then is unable to compile, as
>> > this
>> > creat
Hello,
On Sun, 2016-05-29 at 21:12 +0200, Uros Bizjak wrote:
> Hello!
>
> >
> > When trying to compile using -march=native on a VIA nano CPU, gcc
> > selects "-march=core2" "-mtune=i386" then is unable to compile, as
> > this
> > creates a conflicts between 32 bits and 64 bits compilation modes,
Hello!
> When trying to compile using -march=native on a VIA nano CPU, gcc
> selects "-march=core2" "-mtune=i386" then is unable to compile, as this
> creates a conflicts between 32 bits and 64 bits compilation modes, as
> show by the following test:
[...]
> --- gcc/config/i386/driver-i386.c.ori
When trying to compile using -march=native on a VIA nano CPU, gcc
selects "-march=core2" "-mtune=i386" then is unable to compile, as this
creates a conflicts between 32 bits and 64 bits compilation modes, as
show by the following test:
# echo 'int main(){return 0;}' > test.c && gcc -march=native -
