This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Successful bootstrap and install of gcc (GCC) 6.3.0 on aarch64-unknown-linux-gnu


On 25/01/17 19:02, Aaro Koskinen wrote:
> Configured with: ../gcc-6.3.0/configure --with-arch=armv8-a+crc --with-cpu=cortex-a53 --disable-multilib --disable-nls --prefix=/home/aaro/gcctest/newcompiler --enable-languages=c,c++ --host=aarch64-unknown-linux-gnu --build=aarch64-unknown-linux-gnu --target=aarch64-unknown-linux-gnu --with-system-zlib --with-sysroot=/
> host:	  raspberrypi-3
> distro:	  los.git rootfs=96c66f native=96c66f
> kernel:	  Linux 4.9.0-rpi3-los_8e2f1c
> binutils: GNU binutils 2.27
> make:	  GNU Make 4.2.1
> libc:	  GNU C Library (GNU libc) stable release version 2.24
> zlib:	  1.2.8
> mpfr:	  3.1.3
> gmp:	  60000
...
> processor	: 0
> BogoMIPS	: 38.40
> Features	: fp asimd evtstrm crc32
> CPU implementer	: 0x41
> CPU architecture: 8
> CPU variant	: 0x0
> CPU part	: 0xd03
> CPU revision	: 4

this seems to be an r0p4 revision of cortex-a53, if you
use your toolchain to build binaries that are potentially
executed on such hw then i think the safe way is to
configure gcc with

--enable-fix-cortex-a53-835769
--enable-fix-cortex-a53-843419

since it may not be easy to tell what software is
affected on a case by case basis (there are flags to
turn these on/off at compile time if you want to go
that way).


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]