mirror of
https://github.com/tinygo-org/tinygo.git
synced 2026-08-07 12:33: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.
37 lines
836 B
Go
37 lines
836 B
Go
// +build fe310,qemu
|
|
|
|
package runtime
|
|
|
|
import (
|
|
"runtime/volatile"
|
|
"unsafe"
|
|
)
|
|
|
|
// Special memory-mapped device to exit tests, created by SiFive.
|
|
var testExit = (*volatile.Register32)(unsafe.Pointer(uintptr(0x100000)))
|
|
|
|
// ticksToNanoseconds converts CLINT ticks (at 100ns per tick) to nanoseconds.
|
|
func ticksToNanoseconds(ticks timeUnit) int64 {
|
|
return int64(ticks) * 100
|
|
}
|
|
|
|
// nanosecondsToTicks converts nanoseconds to CLINT ticks (at 100ns per tick).
|
|
func nanosecondsToTicks(ns int64) timeUnit {
|
|
return timeUnit(ns / 100)
|
|
}
|
|
|
|
func abort() {
|
|
exit(1)
|
|
}
|
|
|
|
func exit(code int) {
|
|
if code == 0 {
|
|
// Signal a successful exit.
|
|
testExit.Set(0x5555) // FINISHER_PASS
|
|
} else {
|
|
// Signal a failure. The exit code is stored in the upper 16 bits of the
|
|
// 32 bit value.
|
|
testExit.Set(uint32(code)<<16 | 0x3333) // FINISHER_FAIL
|
|
}
|
|
}
|