Re: [radeonhd] Re: Updated R5xx 3D Programming Guide

2008-04-08 Thread Jerome Glisse
On Sat, 05 Apr 2008 15:58:45 +0200 Syren Baran [EMAIL PROTECTED] wrote: Shouldt we start with the first thing first? That would be the assembler, just turning the opcodes into binary form. Well, and some way to transfer the binary to the gpu. That shouldnt be much of a hassle (the command

Re: [radeonhd] Re: Updated R5xx 3D Programming Guide

2008-04-08 Thread Syren Baran
Am Dienstag, den 08.04.2008, 19:39 +0200 schrieb Jerome Glisse: GPU are not a CPU, programming them is far more complexe than programming CPU, you have to handle things that CPU do for you. For instance you have setup how data are routed to GPU. True, thats still the main problem i see.

Re: [radeonhd] Re: Updated R5xx 3D Programming Guide

2008-04-08 Thread Jerome Glisse
On Wed, 09 Apr 2008 00:36:28 +0200 Syren Baran [EMAIL PROTECTED] wrote: Am Dienstag, den 08.04.2008, 19:39 +0200 schrieb Jerome Glisse: GPU are not a CPU, programming them is far more complexe than programming CPU, you have to handle things that CPU do for you. For instance you have

Re: [radeonhd] Re: Updated R5xx 3D Programming Guide

2008-04-08 Thread Zack Rusin
On Tuesday 08 April 2008 07:24:40 pm Jerome Glisse wrote: I just want to be sure that you are aware of the limitation of GPU hw, it should not be seen as CPU and so not be tackle like a CPU. Compiler we are aiming for should be able to translate TGSI in GPU opcode. I am yet not sure on win we

Re: [radeonhd] Re: Updated R5xx 3D Programming Guide

2008-04-05 Thread Syren Baran
Am Mittwoch, den 02.04.2008, 09:02 -0400 schrieb Alex Deucher: Anybody have futher for compilers for the GPU´s? Preferably open compilers. There is work to integrate LLVM into mesa. Shouldt we start with the first thing first? That would be the assembler, just turning the opcodes into