> vx32 converts SIGFPE to the SIMD SSE/SSE2 trap 19, but
> 9vx expects only x87.
Ah. So that explains where the 19 came from.
I had wondered how I got that wrong. ;-)
Vx32 originally disallowed the x87 so that the
VM execution would be more deterministic,
but it was easier to turn on x87 support
>> it probablly could. but i worry about low-power x86
>> devices. perhaps floating point is just not an issue
>> on them?
>
> do they support fp at all, or just x87 not sse?
> i can't remember what is on the little soekris boards
according to wikipedia, geode before the nx don't support sse,
b
> it probablly could. but i worry about low-power x86
> devices. perhaps floating point is just not an issue
> on them?
do they support fp at all, or just x87 not sse?
i can't remember what is on the little soekris boards
> vx32 converts SIGFPE to the SIMD SSE/SSE2 trap 19, but
> 9vx expects only x87.
>
> i had wondered the other day whether there were AMD/Intel processors
> in common use that supported x87 but not SSE/SSE2. should 8c start
> using SSE as the plan 9 amd64 compiler does? could it support that
> ex
> Any chance this [fp signals in APE] is some 9vx issue?
vx32 converts SIGFPE to the SIMD SSE/SSE2 trap 19, but
9vx expects only x87.
i had wondered the other day whether there were AMD/Intel processors
in common use that supported x87 but not SSE/SSE2. should 8c start
using SSE as the plan 9 am
> Any chance this is some 9vx issue? I tried the test code below it
> worked in 9grid.jp ,but gave the following message in 9vx
You are caught in quite a tangled web.
The hardware gets a floating point trap,
Linux/BSD/OS X turns it into a SIGFPE,
vx32 turns it back into a hardware trap,
Plan 9 t
On 7/4/08, Charles Forsyth <[EMAIL PROTECTED]> wrote:
> > When I trigger a division by zero the handler is not called, I just
> > get trap 19 message.
>
>
> if i do a floating-point division by zero, the SIGFPE signal handler is
> called,
> because ape's signal recognises the initial "sys: fp: "
> When I trigger a division by zero the handler is not called, I just
> get trap 19 message.
if i do a floating-point division by zero, the SIGFPE signal handler is called,
because ape's signal recognises the initial "sys: fp: ". (ie, it works for me.)
it doesn't work for an integer division by
Hi
Can anybody point me to a document discussing the signal handling in APE.
One of the program I am porting is using signal to intercept SIGFPE.
It works under linux, but after I ported it to plan9 it is no longer
working.
I was able to intercept SIGINT.
When I trigger a division by zero the ha
