search for: loopvectorisationanalysi

...ment tree, with plenty of TODOs and unfinished experiments > > * We haven't posted our clang changes yet > > I don't mind FIXMEs or TODOs, but I did see a lot of spurious name > changes, enum value moves (breaking old binaries) and a lot of new > high-level passes (LoopVectorisationAnalysis) which will need a long > review on their own before we even start thinking about SVE. > > I recommend you guys separate the refactoring from the implementation > and try to upstream the initial and uncontroversial refactorings (name > changes, etc), as well as move out the curr...

...ished experiments > > > * We haven't posted our clang changes yet > > > > I don't mind FIXMEs or TODOs, but I did see a lot of spurious name > > changes, enum value moves (breaking old binaries) and a lot of new > > high-level passes (LoopVectorisationAnalysis) which will need a long > > review on their own before we even start thinking about SVE. > > > > I recommend you guys separate the refactoring from the > implementation > > and try to upstream the initial and uncontroversial refactorings > (name &gt...

Hi, We've been working for the last two years on support for ARM's Scalable Vector Extension in LLVM, and we'd like to upstream our work. We've had to make several design decisions without community input, and would like to discuss the major changes we've made. To help with the discussions, I've attached a technical document (also in plain text below) to describe the