summaryrefslogtreecommitdiff
path: root/src/thread/or1k/clone.s
AgeCommit message (Collapse)AuthorLines
2025-02-21clone: clear the frame pointer in the child process on relevant portsAlex Rønne Petersen-1/+2
This just mirrors what is done in the start code for the affected ports, as well as what is already done for the three x86 ports. Clearing the frame pointer helps protect FP-based unwinders from wrongly attempting to traverse into the parent thread's call frame stack.
2025-02-21clone: align the given stack pointer on or1k and riscvAlex Rønne Petersen-0/+2
This was an oversight specific to these archs; others have always aligned the new stack pointer correctly.
2018-09-12make arch __clone backends hiddenRich Felker-0/+1
these are not a public interface and are not intended to be callable from anywhere but the public clone function or other places in libc.
2014-07-18add or1k (OpenRISC 1000) architecture portStefan Kristiansson-0/+30
With the exception of a fenv implementation, the port is fully featured. The port has been tested in or1ksim, the golden reference functional simulator for OpenRISC 1000. It passes all libc-test tests (except the math tests that requires a fenv implementation). The port assumes an or1k implementation that has support for atomic instructions (l.lwa/l.swa). Although it passes all the libc-test tests, the port is still in an experimental state, and has yet experienced very little 'real-world' use.