If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

further examination led to discovery that 5ab82e0ccf84855e9311ebfc58d1b57b437ed991 is the sole root of the problem as git master works well with just this one patch reverted

if you want to test r600 llvm compiler, you need to fetch latest revision tree from here : http://cgit.freedesktop.org/~tstellar/llvm/ and build the AMDGPU backend (please ensure you always pull it when you pull mesa)
R600 llvm backend development happened under src/gallium/drivers/radeon but it has been promoted to experimental status and is now part of llvm tree.
Sorry for the inconvenience, the backend and the tgsi-to-llvm pass are still work in progress and API is not stable atm.

if you want to test r600 llvm compiler, you need to fetch latest revision tree from here : http://cgit.freedesktop.org/~tstellar/llvm/ and build the AMDGPU backend (please ensure you always pull it when you pull mesa)
R600 llvm backend development happened under src/gallium/drivers/radeon but it has been promoted to experimental status and is now part of llvm tree.
Sorry for the inconvenience, the backend and the tgsi-to-llvm pass are still work in progress and API is not stable atm.

Well anyone using stuff from git should expect API change now and then so no problem there Hence the changes took place and I use only llvm 3.1-r2 I guess the issues would come up sooner or later. Anyways I fetched llvm git repo from above source, but please tell me how do I make sure I compile AMDGPU backend You mentioned as configure script nor README do not tell anything about amd at all... Whould changing repo name in the llvm-9999 ebuild be enough or I need to take some additional steps too? http://gentoo-portage.com/sys-devel/llvm

I'm not familiar with portage so I don't know how to change the ebuild to install llvm 3.2 on your system. I do actually think that installing a development version of llvm system-wide can break things, it's better if you install it somewhere in your HOME. I do this and use a slightly modified version of ~/.bashrc that adds local llvm-config to my PATH.

A detailed how to could be :
git clone git://people.freedesktop.org/~tstellar/llvm
cd llvm
./configure --enable-experimental-targets=AMDGPU --enable-assertions --prefix=/home/user/llvmbin
make && make install

then appebd "PATH=/home/vlj/llvmbin/bin/:$PATH" to your ~/.bashrc file, then restart bash (ie restart your konsole/gnome-terminal/...). You can now reconfigure and rebuild mesa as usual.

I'm not familiar with portage so I don't know how to change the ebuild to install llvm 3.2 on your system. I do actually think that installing a development version of llvm system-wide can break things, it's better if you install it somewhere in your HOME. I do this and use a slightly modified version of ~/.bashrc that adds local llvm-config to my PATH.

A detailed how to could be :
git clone git://people.freedesktop.org/~tstellar/llvm
cd llvm
./configure --enable-experimental-targets=AMDGPU --enable-assertions --prefix=/home/user/llvmbin
make && make install

then appebd "PATH=/home/vlj/llvmbin/bin/:$PATH" to your ~/.bashrc file, then restart bash (ie restart your konsole/gnome-terminal/...). You can now reconfigure and rebuild mesa as usual.

Thanks for Your hints. After that I found http://dri.freedesktop.org/wiki/GalliumCompute which even allows one to experiment with opencl while at it Breaking stuff is likely and happens in Gentoo all the time like few days ago when mysql was updated from version 5.1 to 5.5 in unstable, but for those cases there is this quite nice tool "revdep-rebuild" that preaty much finds all broken libraries and rebuilds broken packages so it is not all that big of an issue as in this case it was like 4 of them for me. Breakage is ussually hardly noticable cause of use of "-Wl,--as-needed" during linking by default which limits number of libs packages it using I would say by half.
However it seems that when I enable AMDGPU using the tree I get linking error specific to the use of as-needed or fvisibility

if you want to test r600 llvm compiler, you need to fetch latest revision tree from here : http://cgit.freedesktop.org/~tstellar/llvm/ and build the AMDGPU backend (please ensure you always pull it when you pull mesa)
R600 llvm backend development happened under src/gallium/drivers/radeon but it has been promoted to experimental status and is now part of llvm tree.
Sorry for the inconvenience, the backend and the tgsi-to-llvm pass are still work in progress and API is not stable atm.

Does any of indirect* branches is suitable for testing or they need some more time?

The kernel driver will attempt to free up enough vram to honor the request by migrating other buffers out of vram, but if there is still not enough room, you'll end up with gart. Depending on how much migration has to take place, it's sometimes better to just use gart in the first place. There are no simple answers.

Newer asics have a lot of vram so it's less of an issue to waste a little more space for the gart page table. This gives us some additional gart space before having to migrate to non-gart system ram for games, etc. where we use up most of vram.