Displaying 9 results from an estimated 9 matches for "hasmips64".
2015 Sep 23
2
The Trouble with Triples
...e N64 ABI. N32 is a Triple::mips64/mips64el that should behave as the Triple::mips/mipsel cases do.
* DataFlowSanitizer: Is heading down the same road but hasn't implemented O32/N32 yet.
* MemorySanitizer: Is heading down the same road but hasn't implemented O32/N32 yet.
* Many places where hasMips64*() or isGP64bit() are used in the backend.
* MSA intrinsic lowering
* Legalization configuration
* Instruction selection
* MipsTargetLowering::getOptimalMemOpType()
* And many more. I can provide more detail if you want.
Other notables:
* RuntimeDyldELF gets it right but only because it...
2015 Sep 23
2
The Trouble with Triples
...e N64 ABI. N32 is a Triple::mips64/mips64el that should behave as the Triple::mips/mipsel cases do.
* DataFlowSanitizer: Is heading down the same road but hasn't implemented O32/N32 yet.
* MemorySanitizer: Is heading down the same road but hasn't implemented O32/N32 yet.
* Many places where hasMips64*() or isGP64bit() are used in the backend.
* MSA intrinsic lowering
* Legalization configuration
* Instruction selection
* MipsTargetLowering::getOptimalMemOpType()
* And many more. I can provide more detail if you want.
Other notables:
* RuntimeDyldELF gets it right but only because it...
2015 Sep 23
4
The Trouble with Triples
...e N64 ABI. N32 is a Triple::mips64/mips64el that should behave as the Triple::mips/mipsel cases do.
* DataFlowSanitizer: Is heading down the same road but hasn't implemented O32/N32 yet.
* MemorySanitizer: Is heading down the same road but hasn't implemented O32/N32 yet.
* Many places where hasMips64*() or isGP64bit() are used in the backend.
* MSA intrinsic lowering
* Legalization configuration
* Instruction selection
* MipsTargetLowering::getOptimalMemOpType()
* And many more. I can provide more detail if you want.
Other notables:
* RuntimeDyldELF gets it right but only because it...
2015 Sep 23
4
The Trouble with Triples
...:mips64/mips64el that should behave as the Triple::mips/mipsel cases do.
· DataFlowSanitizer: Is heading down the same road but hasn't implemented O32/N32 yet.
· MemorySanitizer: Is heading down the same road but hasn't implemented O32/N32 yet.
· Many places where hasMips64*() or isGP64bit() are used in the backend.
o MSA intrinsic lowering
o Legalization configuration
o Instruction selection
o MipsTargetLowering::getOptimalMemOpType()
o And many more. I can provide more detail if you want.
Other notables:
· RuntimeDyldELF gets it right but on...
2015 Sep 24
3
The Trouble with Triples
...e N64 ABI. N32 is a Triple::mips64/mips64el that should behave as the Triple::mips/mipsel cases do.
* DataFlowSanitizer: Is heading down the same road but hasn't implemented O32/N32 yet.
* MemorySanitizer: Is heading down the same road but hasn't implemented O32/N32 yet.
* Many places where hasMips64*() or isGP64bit() are used in the backend.
* MSA intrinsic lowering
* Legalization configuration
* Instruction selection
* MipsTargetLowering::getOptimalMemOpType()
* And many more. I can provide more detail if you want.
Other notables:
* RuntimeDyldELF gets it right but only because it...
2013 Apr 01
0
[LLVMdev] proposed change to class BasicTTI and dual mode mips16/32 working
...ableMipsTailCalls("enable-mips-tail-calls", cl::Hidden,
MipsSETargetLowering::MipsSETargetLowering(MipsTargetMachine &TM)
: MipsTargetLowering(TM) {
// Set up the register classes
+
+ clearRegisterClasses();
+
addRegisterClass(MVT::i32, &Mips::CPURegsRegClass);
if (HasMips64)
diff --git a/lib/Target/Mips/MipsSubtarget.cpp b/lib/Target/Mips/MipsSubtarget.cpp
index e11e5d1..4f56bd5 100644
--- a/lib/Target/Mips/MipsSubtarget.cpp
+++ b/lib/Target/Mips/MipsSubtarget.cpp
@@ -11,29 +11,47 @@
//
//===----------------------------------------------------------------------===//...
2013 Apr 01
3
[LLVMdev] proposed change to class BasicTTI and dual mode mips16/32 working
On Thu, Mar 28, 2013 at 12:22 PM, Nadav Rotem <nrotem at apple.com> wrote:
> IMHO the right way to handle target function attributes is to
> re-initialize the target machine and TTI for every function (if the
> attributes changed). Do you have another solution in mind ?
I don't really understand this.
TargetMachine and TTI may be quite expensive to initialize. Doing so for
2015 Sep 23
3
The Trouble with Triples
...:mips64/mips64el that should behave as the Triple::mips/mipsel cases do.
• DataFlowSanitizer: Is heading down the same road but hasn't implemented O32/N32 yet.
• MemorySanitizer: Is heading down the same road but hasn't implemented O32/N32 yet.
• Many places where hasMips64*() or isGP64bit() are used in the backend.
o MSA intrinsic lowering
o Legalization configuration
o Instruction selection
o MipsTargetLowering::getOptimalMemOpType()
o And many more. I can provide more detail if you want.
Other notables:
• RuntimeDyldELF gets it right but on...
2015 Sep 22
2
The Trouble with Triples
>> Here's the line of thought that I'd like people to start with:
>> * Triples don't describe the target. They look like they should, but they
>> don't. They're really just arbitrary strings.
>
>Triples are used as a starting point, but no more.
I disagree with this but for now let's assume it's true. The starting point is
incorrect because