Searched hist:"953 a7d7c61f3b2f5351dfe668510ec782ae282e8" (Results 1 – 6 of 6) sorted by relevance
| /freebsd/sys/arm64/include/ |
| H A D | vfp.h | diff 953a7d7c61f3b2f5351dfe668510ec782ae282e8 Tue Mar 09 20:11:40 CET 2021 Alex Richardson <arichardson@FreeBSD.org> Arch64: Clear VFP state on execve()
I noticed that many of the math-related tests were failing on AArch64.
After a lot of debugging, I noticed that the floating point exception flags
were not being reset when starting a new process. This change resets the
VFP inside exec_setregs() to ensure no VFP register state is leaked from
parent processes to children.
This commit also moves the clearing of fpcr that was added in 65618fdda0f27
from fork() to execve() since that makes more sense: fork() can retain
current register values, but execve() should result in a well-defined
clean state.
Reviewed By: andrew
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D29060
|
| /freebsd/sys/arm64/arm64/ |
| H A D | vfp.c | diff 953a7d7c61f3b2f5351dfe668510ec782ae282e8 Tue Mar 09 20:11:40 CET 2021 Alex Richardson <arichardson@FreeBSD.org> Arch64: Clear VFP state on execve()
I noticed that many of the math-related tests were failing on AArch64.
After a lot of debugging, I noticed that the floating point exception flags
were not being reset when starting a new process. This change resets the
VFP inside exec_setregs() to ensure no VFP register state is leaked from
parent processes to children.
This commit also moves the clearing of fpcr that was added in 65618fdda0f27
from fork() to execve() since that makes more sense: fork() can retain
current register values, but execve() should result in a well-defined
clean state.
Reviewed By: andrew
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D29060
|
| H A D | elf32_machdep.c | diff 953a7d7c61f3b2f5351dfe668510ec782ae282e8 Tue Mar 09 20:11:40 CET 2021 Alex Richardson <arichardson@FreeBSD.org> Arch64: Clear VFP state on execve()
I noticed that many of the math-related tests were failing on AArch64.
After a lot of debugging, I noticed that the floating point exception flags
were not being reset when starting a new process. This change resets the
VFP inside exec_setregs() to ensure no VFP register state is leaked from
parent processes to children.
This commit also moves the clearing of fpcr that was added in 65618fdda0f27
from fork() to execve() since that makes more sense: fork() can retain
current register values, but execve() should result in a well-defined
clean state.
Reviewed By: andrew
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D29060
|
| H A D | vm_machdep.c | diff 953a7d7c61f3b2f5351dfe668510ec782ae282e8 Tue Mar 09 20:11:40 CET 2021 Alex Richardson <arichardson@FreeBSD.org> Arch64: Clear VFP state on execve()
I noticed that many of the math-related tests were failing on AArch64.
After a lot of debugging, I noticed that the floating point exception flags
were not being reset when starting a new process. This change resets the
VFP inside exec_setregs() to ensure no VFP register state is leaked from
parent processes to children.
This commit also moves the clearing of fpcr that was added in 65618fdda0f27
from fork() to execve() since that makes more sense: fork() can retain
current register values, but execve() should result in a well-defined
clean state.
Reviewed By: andrew
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D29060
|
| H A D | machdep.c | diff 953a7d7c61f3b2f5351dfe668510ec782ae282e8 Tue Mar 09 20:11:40 CET 2021 Alex Richardson <arichardson@FreeBSD.org> Arch64: Clear VFP state on execve()
I noticed that many of the math-related tests were failing on AArch64.
After a lot of debugging, I noticed that the floating point exception flags
were not being reset when starting a new process. This change resets the
VFP inside exec_setregs() to ensure no VFP register state is leaked from
parent processes to children.
This commit also moves the clearing of fpcr that was added in 65618fdda0f27
from fork() to execve() since that makes more sense: fork() can retain
current register values, but execve() should result in a well-defined
clean state.
Reviewed By: andrew
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D29060
|
| /freebsd/sys/arm64/linux/ |
| H A D | linux_sysvec.c | diff 953a7d7c61f3b2f5351dfe668510ec782ae282e8 Tue Mar 09 20:11:40 CET 2021 Alex Richardson <arichardson@FreeBSD.org> Arch64: Clear VFP state on execve()
I noticed that many of the math-related tests were failing on AArch64.
After a lot of debugging, I noticed that the floating point exception flags
were not being reset when starting a new process. This change resets the
VFP inside exec_setregs() to ensure no VFP register state is leaked from
parent processes to children.
This commit also moves the clearing of fpcr that was added in 65618fdda0f27
from fork() to execve() since that makes more sense: fork() can retain
current register values, but execve() should result in a well-defined
clean state.
Reviewed By: andrew
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D29060
|