search for: r206094

Yep, quite right, Evan. Any regalloc differences due to that patch are purely coincidence; -Jim > On Jun 16, 2014, at 10:13 AM, Evan Cheng <evan.cheng at apple.com> wrote: > > Hi Niklas, > > The attached patch has nothing to do with register allocation. r206094 changes how cpu auto-detection is done. I believe it's now the responsibility of the tools (e.g. llc) to detect the cpu. My guess is the proper fix is on the RoboVM side to handle the change. > > Jim, can you confirm? > > Evan > > On Jun 1, 2014, at 1:45 PM, Niklas Therning...

I think we have located the revision which fixes this regression: r206094 (or commit 6bb00df in llvm-mirror on GitHub). I have attached a patch which can be applied to the current release_34 branch (tested against the release_34 branch in llvm-mirror). With this patch the attached reg-alloc-test.ll file doesn't fail with the "LLVM ERROR: ran out of registers dur...

On Fri, Apr 11, 2014 at 3:58 PM, Jim Grosbach <grosbach at apple.com> wrote: > > Now, one additional thing we could do (outside the scope of this proposal) > is also implement a fuzzer of some kind to look for target tests that don’t > have an explicit arch/feature/whatever setting on the RUN line and run it > with all available -mcpu= values and see if it still passes (which

I can confirm that this regression has been fixed in trunk. Should I report this as a bug in 3.4? On Thu, Apr 24, 2014 at 10:17 PM, Quentin Colombet <qcolombet at apple.com>wrote: > Hi Niklas, > > This works for me with trunk r207129. > > We did fix some register allocation issues recently, don’t know which > change fixes the issue though. > > Thanks, > -Quentin