http://llvm.org https://git.amat.us/llvm/atom/test/CodeGen/AArch64?h=release_33 2013-05-04T16:54:07Z 2013-05-04T16:54:07Z Tim Northover Tim.Northover@arm.com 2013-05-04T16:54:07Z urn:sha1:79c1c092dfd14703cdd47e96bc5a14d97322ee16 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181120 91177308-0d34-0410-b5e6-96231b3b80d8 2013-05-04T16:54:00Z Tim Northover Tim.Northover@arm.com 2013-05-04T16:54:00Z urn:sha1:cd1b09b25b57c1fb09a50ded1d6852a5a1cb6377 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181119 91177308-0d34-0410-b5e6-96231b3b80d8 2013-05-04T16:53:53Z Tim Northover Tim.Northover@arm.com 2013-05-04T16:53:53Z urn:sha1:b2efdde06c00023287255d9a09861e43fb5efebd git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181118 91177308-0d34-0410-b5e6-96231b3b80d8 2013-05-04T16:53:46Z Tim Northover Tim.Northover@arm.com 2013-05-04T16:53:46Z urn:sha1:45db92038bf540fbbd8dfe5dff520aa8566d7cef The MOVZ/MOVK instruction sequence may not be the most efficient (a literal-pool load could be better) but adding that would require reinstating the ConstantIslands pass. For now the sequence is correct, and that's enough. Beware, as of commit GNU ld does not appear to support the relocations needed for this. Its primary purpose (for now) will be to support JITed code, since in that case there is no guarantee of where your code will end up in memory relative to external symbols it references. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@181117 91177308-0d34-0410-b5e6-96231b3b80d8 2013-04-12T04:06:46Z Nico Rieck nico.rieck@gmail.com 2013-04-12T04:06:46Z urn:sha1:f89da7210b09a0a0f7c9ee216cd54dca03c6b64a git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@179361 91177308-0d34-0410-b5e6-96231b3b80d8 2013-04-08T08:40:41Z Tim Northover Tim.Northover@arm.com 2013-04-08T08:40:41Z urn:sha1:211ffd242df8bacf4cbe034f5ca7545ab75b45df I've managed to convince myself that AArch64's acquire/release instructions are sufficient to guarantee C++11's required semantics, even in the sequentially-consistent case. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@179005 91177308-0d34-0410-b5e6-96231b3b80d8 2013-03-26T18:56:54Z Hal Finkel hfinkel@anl.gov 2013-03-26T18:56:54Z urn:sha1:8846129f6eb58982a2cac22306c8c9b586084475 The previous algorithm could not deal properly with scavenging multiple virtual registers because it kept only one live virtual -> physical mapping (and iterated through operands in order). Now we don't maintain a current mapping, but rather use replaceRegWith to completely remove the virtual register as soon as the mapping is established. In order to allow the register scavenger to return a physical register killed by an instruction for definition by that same instruction, we now call RS->forward(I) prior to eliminating virtual registers defined in I. This requires a minor update to forward to ignore virtual registers. These new features will be tested in forthcoming commits. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@178058 91177308-0d34-0410-b5e6-96231b3b80d8 2013-03-09T18:25:40Z Benjamin Kramer benny.kra@googlemail.com 2013-03-09T18:25:40Z urn:sha1:1cb47b9afe77231d6b87b8445dfec475fb5e59cd git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176772 91177308-0d34-0410-b5e6-96231b3b80d8 2013-03-08T15:27:30Z Tim Northover Tim.Northover@arm.com 2013-03-08T15:27:30Z urn:sha1:fa3dc9ffbb5d8b9bb742940388dd14fc5f282362 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176692 91177308-0d34-0410-b5e6-96231b3b80d8 2013-03-08T13:55:07Z Tim Northover Tim.Northover@arm.com 2013-03-08T13:55:07Z urn:sha1:69fe178f7781fa3c01d013ac7b7858926064f6ca Patch based on Mans Rullgard's. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176688 91177308-0d34-0410-b5e6-96231b3b80d8