| 1 |
On Tue, Sep 21, 2010 at 4:52 PM, Dan Reidy <dubkat@×××××.com> wrote: |
| 2 |
> On 09/21/2010 02:54 PM, Paul Hartman wrote: |
| 3 |
>> add to USE "graphite" |
| 4 |
>> add to CFLAGS "-floop-interchange -floop-strip-mine -floop-block" |
| 5 |
> doesn't this also need -fgraphite added ? |
| 6 |
|
| 7 |
In GCC 4.4.4 at least, that is undocumented. In docs sources |
| 8 |
(gcc/common.opt) there is this section: |
| 9 |
|
| 10 |
; This option is not documented yet as its semantics will change. |
| 11 |
fgraphite |
| 12 |
Common Report Var(flag_graphite) |
| 13 |
Enable in and out of Graphite representation |
| 14 |
|
| 15 |
floop-strip-mine |
| 16 |
Common Report Var(flag_loop_strip_mine) Optimization |
| 17 |
Enable Loop Strip Mining transformation |
| 18 |
|
| 19 |
floop-interchange |
| 20 |
Common Report Var(flag_loop_interchange) Optimization |
| 21 |
Enable Loop Interchange transformation |
| 22 |
|
| 23 |
floop-block |
| 24 |
Common Report Var(flag_loop_block) Optimization |
| 25 |
Enable Loop Blocking transformation |
| 26 |
|
| 27 |
; This option is not documented as it does not perform any useful optimization. |
| 28 |
fgraphite-identity |
| 29 |
Common Report Var(flag_graphite_identity) Optimization |
| 30 |
Enable Graphite Identity transformation |
| 31 |
|
| 32 |
|
| 33 |
And I found this (more than 1 year old) mailing list message: |
| 34 |
http://www.mailinglistarchive.com/gcc@×××××××.org/msg26371.html |
| 35 |
where Sebastian Pop states "These options are intentionally not |
| 36 |
documented: they should not be used by programmers." |
| 37 |
|
| 38 |
But maybe things have changed for gcc 4.5 (I haven't gone to 4.5 yet |
| 39 |
so don't have the sources on my machine). Maybe someone else can |
| 40 |
consult the newer docs to see if they've changed. |
Archives