https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69614
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2016-02-02
CC| |ktkachov at gcc dot gnu.org
Known to work| |4.9.4, 5.3.1
Ever confirmed|0 |1
--- Comment #1 from ktkachov at gcc dot gnu.org ---
Reproduced with the command line:
-Os -fno-expensive-optimizations -fschedule-insns -mtpcs-leaf-frame
-fira-algorithm=priority -march=armv7-a -mfloat-abi=hard -marm -mfpu=vfpv4
Note that you didn't specify a --with-fpu value in your gcc configuration and
didn't use an -mfpu option in your command line, so gcc defaulted to the value
'vfp' for the fpu. For an architecture like armv7-a it's usually more common to
use values like neon or neon-vfpv4 or vfpv4 if you don't want NEON. 'vfp' is a
very old fpu level. Though this particular bug reproduces with -mfpu=vfp as
well.
That's just for future reference if you want a gcc targeting a more realistic
armv7-a setup by default.
