mirror of
https://github.com/tinygo-org/tinygo.git
synced 2026-08-06 03:53:42 +00:00
Ayke van Laethem
98f84a497d
There were a few issues that were causing qemu-system-arm and
qemu-system-riscv to give the wrong exit codes. They are in fact capable
of exiting with 0 or 1 signalled from the running application, but this
functionality wasn't used. This commit changes this in the following
ways:
* It fixes SemiHosting codes, which were incorrectly written in
decimal while they should have been written in hexadecimal (oops!).
* It modifies all the baremetal main functions (aka reset handlers) to
exit with `exit(0)` instead of `abort()`.
* It changes `syscall.Exit` to call `exit(code)` instead of `abort()`
on baremetal targets.
* It adds these new exit functions where necessary, implemented in a
way that signals the correct exit status if running under QEMU.
All in all, this means that `tinygo test` doesn't have to look at the
output of a test to determine the outcome. It can simply look at the
exit code.
33 lines
670 B
Go
33 lines
670 B
Go
// +build k210,!qemu
|
|
|
|
package runtime
|
|
|
|
import (
|
|
"device/riscv"
|
|
)
|
|
|
|
// ticksToNanoseconds converts CPU ticks to nanoseconds.
|
|
func ticksToNanoseconds(ticks timeUnit) int64 {
|
|
// The following calculation is actually the following, but with both sides
|
|
// reduced to reduce the risk of overflow:
|
|
// ticks * 1e9 / (390000000 / 50)
|
|
// 50 is the CLINT divider and 390000000 is the CPU frequency.
|
|
return int64(ticks) * 5000 / 39
|
|
}
|
|
|
|
// nanosecondsToTicks converts nanoseconds to CPU ticks.
|
|
func nanosecondsToTicks(ns int64) timeUnit {
|
|
return timeUnit(ns * 39 / 5000)
|
|
}
|
|
|
|
func exit(code int) {
|
|
abort()
|
|
}
|
|
|
|
func abort() {
|
|
// lock up forever
|
|
for {
|
|
riscv.Asm("wfi")
|
|
}
|
|
}
|