ff07da6ff1
FPU context switching is always performed on demand through the FPU access exception handler. Actual task switching only grants or denies FPU access depending on the current FPU owner. Because RISC-V doesn't have a dedicated FPU access exception, we must catch the Illegal Instruction exception and look for actual FP opcodes. There is no longer a need to allocate FPU storage on the stack for every exception making esf smaller and stack overflows less likely. Signed-off-by: Nicolas Pitre <npitre@baylibre.com> |
||
|---|---|---|
| .. | ||
| data_structures | ||
| drivers | ||
| iterable_sections | ||
| memory_management | ||
| services | ||
| timing_functions | ||
| usermode | ||
| util | ||
| code-relocation.rst | ||
| index.rst | ||
| timeutil.rst | ||