[Mesa3d-dev] Gallium + llvm integration

2008-09-28 Thread Stephane Marchesin
Hi, I'm working on llvm integration in gallium, but I have a small problem with the current design. Basically, the tgsi to llvm translator currently generates calls to library functions (abs(), exp(), log(), ...) at translation time, and now I want to be able to regarget llvm to GPUs. As you can

Re: [Mesa3d-dev] Gallium + llvm integration

2008-09-28 Thread Zack Rusin
On Sunday 28 September 2008 14:34:53 Stephane Marchesin wrote: Hi, I'm working on llvm integration in gallium, Ah, that's great. but I have a small problem with the current design. Basically, the tgsi to llvm translator currently generates calls to library functions (abs(), exp(), log(),

Re: [Mesa3d-dev] Gallium + llvm integration

2008-09-28 Thread Stephane Marchesin
On Sun, Sep 28, 2008 at 8:46 PM, Zack Rusin [EMAIL PROTECTED] wrote: On Sunday 28 September 2008 14:34:53 Stephane Marchesin wrote: Hi, I'm working on llvm integration in gallium, Ah, that's great. but I have a small problem with the current design. Basically, the tgsi to llvm translator

Re: [Mesa3d-dev] Gallium + llvm integration

2008-09-28 Thread Zack Rusin
On Sunday 28 September 2008 15:04:42 Stephane Marchesin wrote: Oh, I'm thinking about doing driver-specific llvm backends here. Yea, that was always my plan. I've realised that the difference between GPUs really didn't allow common intermediate representation. Furthermore, the llvm tablegen

Re: [Mesa3d-dev] Gallium + llvm integration

2008-09-28 Thread Stephane Marchesin
On Sun, Sep 28, 2008 at 11:14 PM, Zack Rusin [EMAIL PROTECTED] wrote: On Sunday 28 September 2008 15:04:42 Stephane Marchesin wrote: Oh, I'm thinking about doing driver-specific llvm backends here. Yea, that was always my plan. I've realised that the difference between GPUs really didn't

[Mesa3d-dev] Gallium-0.2

2008-09-28 Thread Zack Rusin
Hey, I just realized this was never communicated so just a quick note. Keith, Alan and Brian did the bulk of the work to get gallium-0.1 merged with master and the result is gallium-0.2 branch. It's essentially gallium3d on top of master. gallium-0.2 should stay in sync with master from now

[Mesa3d-dev] [Bug 17820] New: copypixrate fails inside Xephyr

2008-09-28 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=17820 Summary: copypixrate fails inside Xephyr Product: Mesa Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: minor Priority: