https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70210
--- Comment #6 from ktkachov at gcc dot gnu.org --- (In reply to Viktor Engelmann from comment #5) > Hmmm the problem isn't related to docker - I get the same problem when I run > gcc on the raspberry directly with -mcpu=armv7l as autoconf does in docker. > yep, armv7l is not a valid argument to -mcpu by design. > When I run gcc manually with -mcpu=cortex-a53, everything is fine. > lscpu says > > Architecture: armv7l > Byte Order: Little Endian > CPU(s): 4 > On-line CPU(s) list: 0-3 > Thread(s) per core: 1 > Core(s) per socket: 4 > Socket(s): 1 > Vendor ID: ARM > Model: 4 > Model name: Cortex-A53 > Stepping: r0p4 > CPU max MHz: 1200.0000 > CPU min MHz: 600.0000 > BogoMIPS: 38.40 > Flags: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva > idivt vfpd32 lpae evtstrm crc32 > > and /proc/cpuinfo is basically the same as the one Andrew Roberts had posted. > Maybe it's a problem in autoconf for passing armv7l (the "Architecture:" > line) to -mcpu.
