Compiler optimization for Geode/Floating Point pipeline

[Brian Carnes]

The developers page on the wiki
(http://wiki.laptop.org/go/Developers_program) mentions:

"compiler optimization: if you are a compiler wizard, we understand that
the Geode lacks a specific back end code scheduler, which limits
performance, particularly FP performance. We'd love to see work go on in
this area which would help everyone."


What aspects of this issue/request for help are still open?  I'll go take
a look at the OLPC build system tonight to see what is being used (late
versions of GCC do have some Geode -mtune/-march modes), but would love to
be hooked into whatever project is addressing this

...Or start my own project if I'm the first to step to the plate on this
issue.  If anyone knows any particularly lengthy floating-point dominated
operations in the current software, let me know and we'll use them as our
metric for improvement.

Thanks,

  Brian