search for: g_mi

...patterns. As we’re starting from a blank slate, we have an opportunity here to think about what we might need from such a framework without the legacy cruft (although we still have the high performance bar to meet). I want to poll the community about what future requirements we have for the GISel G_MI optimizer/combiner. The following are the general requirements we have so far: It should have at least equivalent, but hopefully better runtime/compile time trade off than the DAGCombiner. There needs to be flexibility in the design to allow targets to run subsets of the overall optimizer. For exa...

...e starting from a blank slate, we have an opportunity here to think about what we might need from such a framework without the legacy cruft (although we still have the high performance bar to meet). >> >> I want to poll the community about what future requirements we have for the GISel G_MI optimizer/combiner. The following are the general requirements we have so far: >> >> It should have at least equivalent, but hopefully better runtime/compile time trade off than the DAGCombiner. >> There needs to be flexibility in the design to allow targets to run subsets of the...

...a blank slate, we have an opportunity here to think about what we might need from such a framework without the legacy cruft (although we still have the high performance bar to meet). >>>> >>>> I want to poll the community about what future requirements we have for the GISel G_MI optimizer/combiner. The following are the general requirements we have so far: >>>> >>>> It should have at least equivalent, but hopefully better runtime/compile time trade off than the DAGCombiner. >>>> There needs to be flexibility in the design to allow targe...

...e starting from a blank slate, we have an opportunity here to think about what we might need from such a framework without the legacy cruft (although we still have the high performance bar to meet). >> >> I want to poll the community about what future requirements we have for the GISel G_MI optimizer/combiner. The following are the general requirements we have so far: >> >> It should have at least equivalent, but hopefully better runtime/compile time trade off than the DAGCombiner. >> There needs to be flexibility in the design to allow targets to run subsets of the...

> On Sep 11, 2018, at 7:39 PM, Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 09/11/2018 12:50 PM, Richard Smith via llvm-dev wrote: >> On Mon, 10 Sep 2018 at 18:47, Nicholas Wilson via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> I was going to wait until Neil Trevett got back to me