llvm/lib/Target/NVPTX, branch testinghttp://llvm.orghttps://git.amat.us/llvm/atom/lib/Target/NVPTX?h=testing2013-03-08T15:36:57ZDAGCombiner: Use correct value type for checking legality of BR_CC v32013-03-08T15:36:57ZTom Stellardthomas.stellard@amd.com2013-03-08T15:36:57Zurn:sha1:3ef5383b3537a420c5e2ab3e657c378e5185549d
LegalizeDAG.cpp uses the value of the comparison operands when checking
the legality of BR_CC, so DAGCombiner should do the same.
v2:
- Expand more BR_CC value types for NVPTX
v3:
- Expand correct BR_CC value types for Hexagon, Mips, and XCore.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176694 91177308-0d34-0410-b5e6-96231b3b80d8
ArrayRefize some code. No functionality change.2013-03-07T20:33:29ZBenjamin Kramerbenny.kra@googlemail.com2013-03-07T20:33:29Zurn:sha1:3853f74aba301ef08b699bac2fa8e53230714a58
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176648 91177308-0d34-0410-b5e6-96231b3b80d8
Fix PR104752013-03-01T18:40:30ZMichael Liaomichael.liao@intel.com2013-03-01T18:40:30Zurn:sha1:a6b20ced765b67a85d9219d0c8547fc9c133e14f
- ISD::SHL/SRL/SRA must have either both scalar or both vector operands
but TLI.getShiftAmountTy() so far only return scalar type. As a
result, backend logic assuming that breaks.
- Rename the original TLI.getShiftAmountTy() to
TLI.getScalarShiftAmountTy() and re-define TLI.getShiftAmountTy() to
return target-specificed scalar type or the same vector type as the
1st operand.
- Fix most TICG logic assuming TLI.getShiftAmountTy() a simple scalar
type.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@176364 91177308-0d34-0410-b5e6-96231b3b80d8
Move the eliminateCallFramePseudoInstr method from TargetRegisterInfo2013-02-21T20:05:00ZEli Benderskyeliben@google.com2013-02-21T20:05:00Zurn:sha1:700ed80d3da5e98e05ceb90e9bfb66058581a6db
to TargetFrameLowering, where it belongs. Incidentally, this allows us
to delete some duplicated (and slightly different!) code in TRI.
There are potentially other layering problems that can be cleaned up
as a result, or in a similar manner.
The refactoring was OK'd by Anton Korobeynikov on llvmdev.
Note: this touches the target interfaces, so out-of-tree targets may
be affected.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@175788 91177308-0d34-0410-b5e6-96231b3b80d8
Update TargetLowering ivars for name policy.2013-02-20T21:13:59ZJim Grosbachgrosbach@apple.com2013-02-20T21:13:59Zurn:sha1:3450f800aa65c91f0496816ba6061a422a74c1fe
http://llvm.org/docs/CodingStandards.html#name-types-functions-variables-and-enumerators-properly
ivars should be camel-case and start with an upper-case letter. A few in
TargetLowering were starting with a lower-case letter.
No functional change intended.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@175667 91177308-0d34-0410-b5e6-96231b3b80d8
[NVPTX] Disable vector registers2013-02-12T14:18:49ZJustin Holewinskijholewinski@nvidia.com2013-02-12T14:18:49Zurn:sha1:7eacad03efda36e09ebd96e95d7891cadaaa9087
Vectors were being manually scalarized by the backend. Instead,
let the target-independent code do all of the work. The manual
scalarization was from a time before good target-independent support
for scalarization in LLVM. However, this forces us to specially-handle
vector loads and stores, which we can turn into PTX instructions that
produce/consume multiple operands.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@174968 91177308-0d34-0410-b5e6-96231b3b80d8
[NVPTX] Make address space errors more explicit (llvm_unreachable -> report_fatal_error)2013-02-09T13:34:15ZJustin Holewinskijholewinski@nvidia.com2013-02-09T13:34:15Zurn:sha1:00d9da1ac45429cb69c8b298b9f25e10a4b57813
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@174808 91177308-0d34-0410-b5e6-96231b3b80d8
[PEI] Pass the frame index operand number to the eliminateFrameIndex function.2013-01-31T20:02:54ZChad Rosiermcrosier@apple.com2013-01-31T20:02:54Zurn:sha1:108fb3202af6f500073cdbb7be32c25d7a273a2e
Each target implementation was needlessly recomputing the index.
Part of rdar://13076458
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@174083 91177308-0d34-0410-b5e6-96231b3b80d8
Clean up assignment of CalleeSaveStackSlotSize: get rid of the default and explicitly set this in every target that needs to change it from the default.2013-01-23T16:22:04ZEli Benderskyeliben@google.com2013-01-23T16:22:04Zurn:sha1:e752feee5228bfa33acee35ef9c606ce12f0f173
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@173270 91177308-0d34-0410-b5e6-96231b3b80d8
NVPTX: Stop leaking memory by using a managed constant instead of a new Argument.2013-01-23T15:21:44ZBenjamin Kramerbenny.kra@googlemail.com2013-01-23T15:21:44Zurn:sha1:e735945ad74a4af9772a7d9bb45418b2551fffe9
This is still an egregious hack since we don't have a nice interface for this
kind of thing but should help the valgrind leak check buildbot to become green.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@173267 91177308-0d34-0410-b5e6-96231b3b80d8