| 1 |
On Tue, Sep 21, 2010 at 11:31 AM, Frank Peters <frank.peters@×××××××.net> wrote: |
| 2 |
> On Tue, 21 Sep 2010 02:48:24 +0000 (UTC) |
| 3 |
> Duncan <1i5t5.duncan@×××.net> wrote: |
| 4 |
> |
| 5 |
>> |
| 6 |
>> Personally, I've been waiting for some general level documentation to come |
| 7 |
>> across my radar before I get involved with either of these. |
| 8 |
>> |
| 9 |
> |
| 10 |
> That's always the problem. Documentation for the many gcc options is sparse |
| 11 |
> at best, and because creating comprehensive documentation would be a gigantic |
| 12 |
> task, it will probably always be so. |
| 13 |
|
| 14 |
AFAIK the short-and-sweet versions: |
| 15 |
|
| 16 |
add to USE "graphite" |
| 17 |
add to CFLAGS "-floop-interchange -floop-strip-mine -floop-block" |
| 18 |
|
| 19 |
add to USE "lto" |
| 20 |
add to CFLAGS "-flto" (must also have some form of -O optimization enabled) |
| 21 |
|
| 22 |
What they actually do and when it is appropriate to use or not use |
| 23 |
them is left an as exercise to the reader. :) |
Archives