Vladimir Makarov wrote:
I already did gcc tunning to geode (pipeline description, code costs,
i386 port parameter values) and submitted it to the gcc mainline. As I
know Jakub Julinek was going to backport this code to redhat gcc. So I
can guess that if the right compiler and options are used, it will make
code faster (and several % smaller because -mtune=geode generates
smaller code that any other tuning).
I incorporated changes to GCC 4.3.x (svn) and have a version tuned for
the OLPC. I've been using this as a cross compiler mostly, but a
variation of these changes would make a difference for the OLPC. My
version is very simple, I set the vendor flag to olpc, so you wind up
with an i585-olpc-linux configuration, which seemed right. When
configured for this, you get a stock i586 toolchain that only differs by
supplying the correct machine options to GCC. It's a very simple patch.
It's probably easiest to make a configuration variant of the standard
toolchain, as it makes cross compiling much easier, and would still
deliver a tuned gcc for native compilation. I can cleanup and submit my
changes if people agreed this was the appropriate config triplet for the
OLPC. If not, I can change it to whatever is commonly agreed on as the
best config triplet, I'm pretty used to hacking GCC config code.
My hacked version of as cross-development toolchain for the OLPC
that's tuned for the Geode is at: http://gnash.lulu.com/tools/. I've
been using it for everything I compile for the OLPC.
- rob -
_______________________________________________
Devel mailing list
[email protected]
http://mailman.laptop.org/mailman/listinfo/devel
