Originally posted by lorenzoz
View Post
Announcement
Collapse
No announcement yet.
More AMD RadeonSI Improvements Land In Mesa Git
Collapse
X
-
Originally posted by dungeon View PostWell it is, but building llvm can be also time consumpator that is why i used that repo most of the time I will lose 1 hour daily just to build llvm two times on Athlon 5350 .
I've compiled LLVM maybe 4-5 times today, to find out what's going on and take me 10min on a [email protected].
Code:#!/bin/bash cd /build/llvm && git reset --hard && git clean -xdf && git pull && ./configure --build=i686-linux-gnu \ --prefix=/usr \ --disable-assertions \ --enable-shared \ --enable-optimized \ --with-optimize-option=' -g -O2' \ --enable-libffi \ --enable-shared \ --disable-bindings \ --enable-targets=r600 \ --libdir=/usr/lib/i386-linux-gnu && pkgversion=$(git log -n 1 | grep git-svn-id | cut -c 62-68) && make -j8 && fakeroot checkinstall --install=yes --pkgname=llvm32 --pkgversion=$"{pkgversion}" --pkgarch=i386 --backup=no --nodoc --default && mv -- ./*.deb /build/completed || exit $? exit 0
Thank you.
Comment
-
Originally posted by lorenzoz View PostO_O wow.
I've compiled LLVM maybe 4-5 times today, to find out what's going on and take me 10min on a [email protected].
Code:#!/bin/bash cd /build/llvm && git reset --hard && git clean -xdf && git pull && [B]./configure --build=i686-linux-gnu \[/B] --prefix=/usr \ --disable-assertions \ --enable-shared \ --enable-optimized \ --with-optimize-option=' -g -O2' \ --enable-libffi \ --enable-shared \ --disable-bindings \ --enable-targets=r600 \ --libdir=/usr/lib/i386-linux-gnu && pkgversion=$(git log -n 1 | grep git-svn-id | cut -c 62-68) && make -j8 && fakeroot checkinstall --install=yes --pkgname=llvm32 --pkgversion=$"{pkgversion}" --pkgarch=i386 --backup=no --nodoc --default && mv -- ./*.deb /build/completed || exit $? exit 0
Thank you.
Comment
-
Originally posted by Marc Driftmeyer View PostSeriously? What reason do you have not to tune your arch and tune to -march=bdver2 -mtune=bdver2?
Comment
-
Originally posted by Nobu View PostNot sure what debian's default build flags are, but regardless, it's easier to say something is a bug in the program rather than your build tools if you use the same configuration when building. Otherwise? Some things actually perform better with less aggressive compiler options. Don't know about llvm, specifically, though.
Otherwise ricing gcc is a whole different matter from tuning for the architecture. Ricing gcc is a term used to describe using excessive compiler to flags to "optimize" the code. There are plenty of benchmarks that show little difference in actual performance between a riced built and a stock build.
Comment
-
Originally posted by Nobu View PostSome things actually perform better with less aggressive compiler options. Don't know about llvm, specifically, though.
From my experience those compiler optimizations does not bring anything good when it comes to drivers. For mesa a like to recommend even -O1 if someone wants most of stability together with performance.
And i recommends -Ofast if someone wants most of performance and broken driver Joking a little , do NOT use that for mesa nor llvm !!!
While i recommend using -march=native -mtune=native (this one in particular) for 3bit mesa radeon build because of bugs likely in toolchain.Last edited by dungeon; 04 February 2015, 07:42 PM.
Comment
-
-
Originally posted by Marc DriftmeyerThen why run chroot when you can install locally or /opt or wherever you want the path to be referenced.
Originally posted by Marc DriftmeyerSeriously? What reason do you have not to tune your arch and tune to -march=bdver2 -mtune=bdver2?
Comment
Comment