When I try to edit the description I'm getting timeout errors (maybe because I'm behind a corporate proxy?). I've written the test case below. Please add it to the bug description.
[Test Case]
* Compile the attached source code using your host C compiler.
* Run the resulting binary.
> It should run for 3 seconds and print timer information. (sanity test)
* Compile the attached source code using a PowerPC cross compiler with
static linking enabled (to make the remaining steps simpler).
* Run the resulting binary using the unpatched qemu-user or qemu-user-static
executable for your selected PowerPC architecture.
> It should exit immediately complaining about an unsupported syscall.
* Run the same binary using the patched qemu-user or qemu-user-static
executable for your selected PowerPC architecture.
> It should behave as the host version did.
> If you chose a big-endian PowerPC architecture, the "timer expirations"
output may be "72057594037927936" instead of "1" because the bytes read
were in host byte order instead of target byte order.
When I try to edit the description I'm getting timeout errors (maybe because I'm behind a corporate proxy?). I've written the test case below. Please add it to the bug description.
[Test Case]
* Compile the attached source code using your host C compiler.
* Run the resulting binary.
> It should run for 3 seconds and print timer information. (sanity test)
* Compile the attached source code using a PowerPC cross compiler with
static linking enabled (to make the remaining steps simpler).
* Run the resulting binary using the unpatched qemu-user or qemu-user-static
executable for your selected PowerPC architecture.
> It should exit immediately complaining about an unsupported syscall.
* Run the same binary using the patched qemu-user or qemu-user-static
executable for your selected PowerPC architecture.
> It should behave as the host version did.
> If you chose a big-endian PowerPC architecture, the "timer expirations"
output may be "72057594037927936" instead of "1" because the bytes read
were in host byte order instead of target byte order.