There's a serious inability on your part to participate in a reasonable discussion. I probably shouldn't bother responding, but I'll do it only once more given the lack of meaningful response.
The GLSL compiler, you know, the one that Intel wrote? http://cgit.freedesktop.org/mesa/mesa/tree/src/glsl
It's C++.
You're incorrectly thinking about the piece of r600g that translates some IR to hardware instructions.
I can't tell if that's a particularly sad attempt to dodge a very real difficulty of moving user space code into the kernel, or if you actually don't understand.
I'll assume it's the latter and waste a bit more of my time explaining it to you.
From the kernel documentation (http://git.kernel.org/?p=linux/kerne...g.tmpl;hb=HEAD)
Originally posted by Qaridarium
It's C++.
You're incorrectly thinking about the piece of r600g that translates some IR to hardware instructions.
Originally posted by Qaridarium
I'll assume it's the latter and waste a bit more of my time explaining it to you.
From the kernel documentation (http://git.kernel.org/?p=linux/kerne...g.tmpl;hb=HEAD)
Code:
No floating point or MMX The FPU context is not saved; even in user context the FPU state probably won't correspond with the current process: you would mess with some user process' FPU state. If you really want to do this, you would have to explicitly save/restore the full FPU state (and avoid context switches). It is generally a bad idea; use fixed point arithmetic first.
Comment