search for: registerallocatephysreg

On Fri, Jul 8, 2011 at 9:30 AM, Karel Gardas <karel.gardas at centrum.cz> wrote: > On 07/ 8/11 05:26 PM, Eli Friedman wrote: >> >> Given that revision range, the only remotely likely culprit is 131463. >>  Which basically means that it "broke" because the default target >> features changed. > > And you are right here. 131463 == 131464 which is

On 07/ 8/11 05:26 PM, Eli Friedman wrote: > Given that revision range, the only remotely likely culprit is 131463. > Which basically means that it "broke" because the default target > features changed. And you are right here. 131463 == 131464 which is buggy. 131462 is OK. Thanks, Karel

...nEngine/2003-05-06-LivenessClobber.ll LLVM :: ExecutionEngine/2003-05-07-ArgumentTest.ll LLVM :: ExecutionEngine/2003-06-04-bzip2-bug.ll LLVM :: ExecutionEngine/2003-08-15-AllocaAssertion.ll LLVM :: ExecutionEngine/2003-08-21-EnvironmentTest.ll LLVM :: ExecutionEngine/2003-08-23-RegisterAllocatePhysReg.ll LLVM :: ExecutionEngine/2003-10-18-PHINode-ConstantExpr-CondCode-Failure.ll LLVM :: ExecutionEngine/2005-12-02-TailCallBug.ll LLVM :: ExecutionEngine/hello.ll LLVM :: ExecutionEngine/hello2.ll LLVM :: ExecutionEngine/stubs.ll LLVM :: ExecutionEngine/test-call.ll LLVM...

...ocBug.ll LLVM :: ExecutionEngine/MCJIT/2003-06-04-bzip2-bug.ll LLVM :: ExecutionEngine/MCJIT/2003-06-05-PHIBug.ll LLVM :: ExecutionEngine/MCJIT/2003-08-15-AllocaAssertion.ll LLVM :: ExecutionEngine/MCJIT/2003-08-21-EnvironmentTest.ll LLVM :: ExecutionEngine/MCJIT/2003-08-23-RegisterAllocatePhysReg.ll LLVM :: ExecutionEngine/MCJIT/2003-10-18-PHINode-ConstantExpr-CondCode-Failure.ll LLVM :: ExecutionEngine/MCJIT/2005-12-02-TailCallBug.ll LLVM :: ExecutionEngine/MCJIT/2007-12-10-APIntLoadStore.ll LLVM :: ExecutionEngine/MCJIT/2008-06-05-APInt-OverAShr.ll LLVM :: Execut...

...ivenessClobber.ll >    LLVM :: ExecutionEngine/2003-05-07-ArgumentTest.ll >    LLVM :: ExecutionEngine/2003-06-04-bzip2-bug.ll >    LLVM :: ExecutionEngine/2003-08-15-AllocaAssertion.ll >    LLVM :: ExecutionEngine/2003-08-21-EnvironmentTest.ll >    LLVM :: ExecutionEngine/2003-08-23-RegisterAllocatePhysReg.ll >    LLVM :: > ExecutionEngine/2003-10-18-PHINode-ConstantExpr-CondCode-Failure.ll >    LLVM :: ExecutionEngine/2005-12-02-TailCallBug.ll >    LLVM :: ExecutionEngine/hello.ll >    LLVM :: ExecutionEngine/hello2.ll >    LLVM :: ExecutionEngine/stubs.ll >    LLVM :: Execution...

...but only on Release mode, not Release+Assert: $ grep XPASS final/logs/llvm.check-Phase3-Release.log XPASS: LLVM :: ExecutionEngine/2003-05-06-LivenessClobber.ll (10862 of 14500) XPASS: LLVM :: ExecutionEngine/2003-08-15-AllocaAssertion.ll (10868 of 14500) XPASS: LLVM :: ExecutionEngine/2003-08-23-RegisterAllocatePhysReg.ll (10870 of 14500) Any ideas why this is the case? cheers, --renato -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130605/14d969e7/attachment.html>

...ing release mode, 4 tests XPASS on ARM and I'm guessing is because they were relying on the assert being hit. Unexpected Passing Tests (4): LLVM :: ExecutionEngine/2003-05-06-LivenessClobber.ll LLVM :: ExecutionEngine/2003-08-15-AllocaAssertion.ll LLVM :: ExecutionEngine/2003-08-23-RegisterAllocatePhysReg.ll LLVM :: ExecutionEngine/MCJIT/test-global-init-nonzero-remote.ll Does anyone know what would be another way of testing this on Release mode? Shouldn't we also fail (stop, return non-zero) in Release mode as well? Funny, though, ExecutionEngine/2003-05-06-LivenessClobber.ll does print a...

Hi, This is true for release_34 and trunk. Disabling assertions makes the following tests pass: Unexpected Passing Tests (5): LLVM :: ExecutionEngine/2003-05-06-LivenessClobber.ll LLVM :: ExecutionEngine/2003-08-15-AllocaAssertion.ll LLVM :: ExecutionEngine/2003-08-23-RegisterAllocatePhysReg.ll LLVM :: ExecutionEngine/MCJIT/cross-module-sm-pic-a.ll LLVM :: ExecutionEngine/MCJIT/multi-module-sm-pic-a.ll -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131206/ab8be70a/attachment.html>

On Mon, Jun 18, 2012 at 04:56:53PM -0700, reed kotler wrote: > I don't see any tests in either test or test-suite for -use-mcjit. For ARM, we need to manually switch to use mcjit, say $ make check-all LIT_ARGS=--param=jit_impl=mcjit Regards, chenwj -- Wei-Ren Chen (陳韋任) Computer Systems Lab, Institute of Information Science, Academia Sinica, Taiwan (R.O.C.) Tel:886-2-2788-3799

...ecutionEngine/MCJIT/2003-06-04-bzip2-bug.ll > LLVM :: ExecutionEngine/MCJIT/2003-06-05-PHIBug.ll > LLVM :: ExecutionEngine/MCJIT/2003-08-15-AllocaAssertion.ll > LLVM :: ExecutionEngine/MCJIT/2003-08-21-EnvironmentTest.ll > LLVM :: ExecutionEngine/MCJIT/2003-08-23-RegisterAllocatePhysReg.ll > LLVM :: > ExecutionEngine/MCJIT/2003-10-18-PHINode-ConstantExpr-CondCode-Failure.ll > LLVM :: ExecutionEngine/MCJIT/2005-12-02-TailCallBug.ll > LLVM :: ExecutionEngine/MCJIT/2007-12-10-APIntLoadStore.ll > LLVM :: ExecutionEngine/MCJIT/2008-06-05-APInt-Ove...

...t;>    LLVM :: ExecutionEngine/2003-05-07-ArgumentTest.ll >>    LLVM :: ExecutionEngine/2003-06-04-bzip2-bug.ll >>    LLVM :: ExecutionEngine/2003-08-15-AllocaAssertion.ll >>    LLVM :: ExecutionEngine/2003-08-21-EnvironmentTest.ll >>    LLVM :: ExecutionEngine/2003-08-23-RegisterAllocatePhysReg.ll >>    LLVM :: >> ExecutionEngine/2003-10-18-PHINode-ConstantExpr-CondCode-Failure.ll >>    LLVM :: ExecutionEngine/2005-12-02-TailCallBug.ll >>    LLVM :: ExecutionEngine/hello.ll >>    LLVM :: ExecutionEngine/hello2.ll >>    LLVM :: ExecutionEngine/stubs.ll &...

I don't see any tests in either test or test-suite for -use-mcjit. Are we not testing this yet? There are lots of other llc options. What is our plan for testing these?

...2003-05-11-PHIRegAllocBug.ll LLVM : : ExecutionEngine/2003-06-04-bzip2-bug.ll LLVM : : ExecutionEngine/2003-06-05-PHIBug.ll LLVM : : ExecutionEngine/2003-08-15-AllocaAssertion.ll LLVM : : ExecutionEngine/2003-08-21-EnvironmentTest.ll LLVM : : ExecutionEngine/2003-08-23-RegisterAllocatePhysReg.ll LLVM : : ExecutionEngine/2003-10-18-PHINode-ConstantExpr-CondCode-Failure.ll LLVM : : ExecutionEngine/2005-12-02-TailCallBug.ll LLVM : : ExecutionEngine/hello.ll LLVM : : ExecutionEngine/hello2.ll LLVM : : ExecutionEngine/simplesttest.ll LLVM : : ExecutionEngi...

On Mon, Feb 23, 2009 at 12:12 AM, Aaron Gray < aaronngray.lists at googlemail.com> wrote: > On Sun, Feb 22, 2009 at 11:15 PM, Anton Korobeynikov < > anton at korobeynikov.info> wrote: > >> >> Actually its [configure-stage3-intl] where its hanging. >> >> This can easily be due to inline FP math in the stdlib headers. For >> example - I had to