|author||Rich Felker <firstname.lastname@example.org>||2015-11-09 21:14:07 -0500|
|committer||Rich Felker <email@example.com>||2015-11-09 21:14:07 -0500|
use vfp mnemonics rather than hard-coded opcodes in arm setjmp/longjmp
the code to save/restore vfp registers needs to build even when the configured target does not have fpu; this is because code using vfp fpu (but with the standard soft-float EABI) may call a libc built for a soft-float only, and the EABI considers these registers call-saved when they exist. thus, extra directives are used to force the assembler to allow vfp instructions and to avoid marking the resulting object files as requiring vfp. moving away from using hard-coded opcode words is necessary in order to eventually support producing thumb2-only output for cortex-m. conditional execution of these instructions based on hwcap flags was already implemented. when building for arm (non-thumb) output, the only currently-supported configuration, this commit does not change the code emitted.
Diffstat (limited to 'src/thread/arm/syscall_cp.s')
0 files changed, 0 insertions, 0 deletions