From cTuning.org
Contents |
Ideas
Record IP passes per main input file
""Motivation"": Different main input file can have different IP passes. For example, if one file has only data structure defination but no function, then no IP passes will run, and nothing will be recorded. -- Susgested by Yuanjie Huang
Save XMLs in folder hierarchy
""Motivation"": Trying to save XMLs in one folder while avioding name conflicts results in strange file names and conplex naming rules. It might be a good idea to keep it in folder hierarchy (which clones the source code directory hierarchy in the adapt-xmls dir)like this:
adapt-xmls/
|-- main.c/
| `-- main.xml
`-- susan.c/
|-- susan_edges.xml
`-- susan_smoothing.xml
- ""Pros"": We can find the xml file quickly and easily in programs that handles these XMLs.
- ""Cons"": Some XMLs may lay in a deep directory hierarchy, making editing manually inconvenient.
-- Suggested by Yuanjie Huang
Seperate generic_clone and instrumentation
""Motivation"": These two passes now seem quite twisted... and offering some duplicate functionality from fine-grain tuning. Maybe we could just leave these two passes simpler and thus more flexible by pass reordering? Then if we clone before instrumentation, then the instrumentation passes should target at the clones; while if we instrument before cloning, the instrument should be copied to each cloned function. -- Susgested by Yuanjie Huang
Todos
Under construction ;)