http://llvm.org https://git.amat.us/llvm/atom/test/CodeGen/XCore?h=release_33 2013-04-16T20:05:52Z 2013-04-16T20:05:52Z Richard Osborne richard@xmos.com 2013-04-16T20:05:52Z urn:sha1:13a16284a5a988a85b55f11ca593452e15d373df git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@179621 91177308-0d34-0410-b5e6-96231b3b80d8 2013-04-16T19:56:55Z Richard Osborne richard@xmos.com 2013-04-16T19:56:55Z urn:sha1:db51e31527a4288c38bc948d582e4bcfc76906d8 I intend to extend the test with more offset folding checks git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@179620 91177308-0d34-0410-b5e6-96231b3b80d8 2013-04-16T19:41:19Z Richard Osborne richard@xmos.com 2013-04-16T19:41:19Z urn:sha1:b509b65240859d151a3961b08b403e4f5fad556b git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@179619 91177308-0d34-0410-b5e6-96231b3b80d8 2013-03-18T22:08:16Z David Blaikie dblaikie@gmail.com 2013-03-18T22:08:16Z urn:sha1:4388d58ff4881e4046d0e08add48a83aaf671e8a git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@177327 91177308-0d34-0410-b5e6-96231b3b80d8 2013-03-18T20:31:44Z David Blaikie dblaikie@gmail.com 2013-03-18T20:31:44Z urn:sha1:e68f0b650e32c1993c5d4c92e04cb3d7b7588010 Apparently my final cleanup to use a relevant suffix for these tests before committing r176831 caused them to stop running since lit wasn't configured to run tests with that suffix in those directories (why don't we just have a global suffix list?). So, add the suffix to the relevant directories & fix the test that has bitrotted over the last week due to my debug info schema changes. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@177315 91177308-0d34-0410-b5e6-96231b3b80d8 2013-03-11T22:10:14Z David Blaikie dblaikie@gmail.com 2013-03-11T22:10:14Z urn:sha1:7cf04f3e1256150bea1b6ffe16fd2e98ae265080 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176831 91177308-0d34-0410-b5e6-96231b3b80d8 2012-11-16T21:12:38Z Richard Osborne richard@xmos.com 2012-11-16T21:12:38Z urn:sha1:ccc015d4314e966253668deec2b18a0d3e0cf4c0 An alias to a function should use pc relative addressing. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@168199 91177308-0d34-0410-b5e6-96231b3b80d8 2012-06-13T17:59:12Z Richard Osborne richard@xmos.com 2012-06-13T17:59:12Z urn:sha1:aa08c8b2ba8d684b144ca016de91ad43e033c7c4 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@158409 91177308-0d34-0410-b5e6-96231b3b80d8 2012-04-16T13:49:17Z Chandler Carruth chandlerc@gmail.com 2012-04-16T13:49:17Z urn:sha1:9e67db4af13abb967cae5858502207a43d26bf84 This is mostly to test the waters. I'd like to get results from FNT build bots and other bots running on non-x86 platforms. This feature has been pretty heavily tested over the last few months by me, and it fixes several of the execution time regressions caused by the inlining work by preventing inlining decisions from radically impacting block layout. I've seen very large improvements in yacr2 and ackermann benchmarks, along with the expected noise across all of the benchmark suite whenever code layout changes. I've analyzed all of the regressions and fixed them, or found them to be impossible to fix. See my email to llvmdev for more details. I'd like for this to be in 3.1 as it complements the inliner changes, but if any failures are showing up or anyone has concerns, it is just a flag flip and so can be easily turned off. I'm switching it on tonight to try and get at least one run through various folks' performance suites in case SPEC or something else has serious issues with it. I'll watch bots and revert if anything shows up. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@154816 91177308-0d34-0410-b5e6-96231b3b80d8 2012-04-02T19:44:20Z Rafael Espindola rafael.espindola@gmail.com 2012-04-02T19:44:20Z urn:sha1:ce167840b2408e531fb7616627ff1bf769b4a111 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@153890 91177308-0d34-0410-b5e6-96231b3b80d8