Improve SLP data analysis
The gimple data-analysis code assumes that, during a loop optimisation,
only data references that can be treated as ivs are of interest. This harms
SLP, which isn't really a loop optimisation, but has to be run before ivopts.
We should extend the data-reference code so that loop vs. non-loop behaviour
can be chosen by the caller.
This will help SLP handle functions like libav's ff_put_
Blueprint information
- Status:
- Complete
- Approver:
- Michael Hope
- Priority:
- High
- Drafter:
- Richard Sandiford
- Direction:
- Approved
- Assignee:
- Ira Rosen
- Definition:
- Approved
- Series goal:
- Accepted for 4.6
- Implementation:
-
Implemented
- Milestone target:
-
4.6-2011.10
- Started by
- Ira Rosen
- Completed by
- Michael Hope
Related branches
Related bugs
Sprints
Whiteboard
Headline: The data reference code can now handle loops vs non-loops which helps the straight line vectoriser
Acceptance: https:/
Work Items
Work items:
Implement, upstream: DONE
backport: DONE
Allow read-read dependencies in SLP: TODO
Implement, upstream: DONE
backport: DONE
Dependency tree
* Blueprints in grey have been implemented.
