| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
| |
Update #2859.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The SPARC ABI is a bit special with respect to the floating point context.
The complete floating point context is volatile. Thus, from an ABI point
of view nothing needs to be saved and restored during a context switch.
Instead the floating point context must be saved and restored during
interrupt processing. Historically, the deferred floating point switch was
used for SPARC and the complete floating point context is saved and
restored during a context switch to the new floating point unit owner.
This is a bit dangerous since post-switch actions (e.g. signal handlers)
and context switch extensions may silently corrupt the floating point
context.
The floating point unit is disabled for interrupt handlers. Thus, in case
an interrupt handler uses the floating point unit then this will result in a
trap (INTERNAL_ERROR_ILLEGAL_USE_OF_FLOATING_POINT_UNIT).
In uniprocessor configurations, a lazy floating point context switch is
used. In case an active floating point thread is interrupted (PSR[EF] == 1)
and a thread dispatch is carried out, then this thread is registered as the
floating point owner. When a floating point owner is present during a
context switch, the floating point unit is disabled for the heir thread
(PSR[EF] == 0). The floating point disabled trap checks that the use of the
floating point unit is allowed and saves/restores the floating point context
on demand.
Update #3077.
|
|
|
|
|
|
| |
Add new fatal error INTERNAL_ERROR_ILLEGAL_USE_OF_FLOATING_POINT_UNIT.
Update #3077.
|
|
|
|
|
| |
It is getting harder to prevent the compiler from optimizing away the
recursive function calls.
|
|
|
|
| |
Update #3076.
|
|
|
|
| |
Update #3076.
|
|
|
|
|
|
|
| |
These tests directly or indirectly use fprintf(), etc. which may use the
floating point unit.
Update #3076.
|
|
|
|
| |
Update #3059.
|
|
|
|
| |
Update #3063.
|
|
|
|
|
|
|
| |
These tests directly or indirectly use fprintf(), etc. which may use the
floating point unit.
Update #3076.
|
|
|
|
|
|
|
| |
These tests directly or indirectly use fprintf(), etc. which may use the
floating point unit.
Update #3076.
|
|
|
|
|
|
| |
This avoids an unnecessary use of the floating point unit.
Update #3076.
|
|
|
|
| |
Updates #2859
|
|
|
|
| |
Update #3070.
|
|
|
|
| |
Update #3069.
|
|
|
|
|
|
|
| |
Ensure that the thread processor affinity fits the new scheduler
instance.
Update #3059.
|
|
|
|
| |
Update #3059.
|
|
|
|
| |
Update #3059.
|
|
|
|
|
|
|
|
| |
The set of online processors must be a subset of the thread processor
affinity for the schedulers without arbitrary processor affinity support
to avoid problems in case of processor addition and removal.
Update #3059.
|
|
|
|
| |
Update #3059.
|
|
|
|
| |
Update #3059.
|
|
|
|
| |
Update #3059.
|
|
|
|
|
|
|
|
| |
Implement the Processor_mask via <sys/bitset.h>. Provide
_Processor_mask_To_uint32_t() to enable its use in device specific
routines, e.g. interrupt affinity register in an interrupt controller.
Update #3059.
|
|
|
|
|
|
|
| |
With global stdio streams, a freopen() would close the global stream
object.
Update #3012.
|
|
|
|
| |
Update #3056.
|
|
|
|
| |
Update #3056.
|
|
|
|
| |
Update #3056.
|
|
|
|
|
|
| |
Split smpscheduler03 to run the tests with only one processor.
Update #3056.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
See also:
https://www.gnu.org/software/automake/manual/html_node/Built-Sources-Example.html
|
|
|
|
| |
Close #3036.
|
|
|
|
| |
Close #3032.
|
|
|
|
|
|
|
|
| |
The original CPU_COPY() support of Newlib <sys/cpuset.h> had the
parameters in the wrong order. This is fixed in Newlib since
2017-05-22.
Update #3023.
|
|
|
|
| |
Update #2833.
|
|
|
|
|
|
|
| |
Remove obsolete support for OFILL, OFDEL, NLDLY, CRDLY, BSDLY, VTDLY,
and FFDLY which is not present on FreeBSD and not implemented in Linux.
Update #2833.
|
| |
|
|
|
|
|
| |
Fix excluding `math` when there is a test `mathl`. The shell test
used fails in this case. This patch's approach is much simpler.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Do not use the processor count to determine if SMP is enabled. Instead
use a dedicated configuration option. Enable SMP by default in SMP
configurations.
Add CONFIGURE_DISABLE_SMP_CONFIGURATION to all test which would fail
otherwise.
Update #3001.
|