Displaying 3 results from an estimated 3 matches for "matchaddress".
2014 Sep 18
2
[LLVMdev] RAUW in shift-and reassociation during X86 ISel
...In order to understand the details, I tried to revert the change but the test case still passes which is not very surprising after 6 years :(.
I am seeing a related new bug that causes a load that was stashed on the NodeStack and in RecordedNodes during iSel to get deleted because the RAUW during MatchAddress CSE’s the load.
I am hoping that you’d still remember some of the details of why we need to modify the DAG like this. Thanks.
Adam
2009 Dec 18
2
[LLVMdev] [PATCH] dbgs() Use
...;===== Instruction selection ends:\n");
+ DEBUG(dbgs() << "===== Instruction selection ends:\n");
#endif
CurDAG->RemoveDeadNodes();
@@ -853,7 +853,7 @@
bool is64Bit = Subtarget->is64Bit();
DebugLoc dl = N.getDebugLoc();
DEBUG({
- errs() << "MatchAddress: ";
+ dbgs() << "MatchAddress: ";
AM.dump();
});
// Limit recursion.
@@ -1711,9 +1711,9 @@
#ifndef NDEBUG
DEBUG({
- errs() << std::string(Indent, ' ') << "Selecting: ";
+ dbgs() << std::string(Indent, ...
2018 Jan 18
1
LEAQ instruction path
Hi,
I've been trying to teach LLVM that pointers are 128-bit long, which
segfaults with some seemingly unrelated stacktrace when I try to take an
address of a variable. Since stack saving and loading seems to work fine, I
dare to assume the instruction causing problems there is leaq. Now I've
done a search for leaq of the entire LLVM codebase with no success and I'd
like to know which