Re: Compiling GCC for different x86 CPU generation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2018-07-24 11:14 +0200, U.Mutlu wrote:
> Andrew Janke wrote on 07/24/2018 07:00 AM:
> > Here's my "configure" call:
> > 
> > ../configure \
> 
> Oops, I wouldn't recommend building in a subdir of the source tree;
> the builddir should be outside, for example
>    ../gcc_src/configure ...

Not necessary.  Just don't './configure'.

On 2018-07-24 11:51 +0200, U.Mutlu wrote:
> What happens if you do this:
>    $ gfortran -g -o hello_world hello_world.f90
>    $ gdb --args ./hello_world
>      and in gdb then issue "run", ..., then issue "quit"
> ?

Andrew's problem is that f951 *itself* SIGILLs, not the object
code generated by f951 SIGILLs.

I agree with Marc that the problem is likely to be in MPC/GMP/MPFR.
Use contrib/download_prerequistes to get the source code of them,
and try to compile GCC with --enable-bootstrap.

--disable-bootstrap is worse since the result will be more likely
contaminated by host.
-- 
Xi Ruoyao <ryxi@xxxxxxxxxxxxxxxxx>
School of Aerospace Science and Technology, Xidian University



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux