Displaying 6 results from an estimated 6 matches for "isstore".
Did you mean:
istore
2020 Sep 10
2
Change prototype for TargetInstrInfo::foldMemoryOperandImpl
....
*** Bad machine code: Missing mayLoad flag ***
which comes from:
// Check the MachineMemOperands for basic consistency.
for (MachineMemOperand *Op : MI->memoperands()) {
if (Op->isLoad() && !MI->mayLoad())
report("Missing mayLoad flag", MI);
if (Op->isStore() && !MI->mayStore())
report("Missing mayStore flag", MI);
}
The MI is ARM::tBL, and it doesn't have mayLoad set, which hits the
assert in MachineVerifier, since it still has memory operands attached
by foldMemoryOperand.
I have attached patch (changes to foldMemor...
2009 Sep 14
2
[LLVMdev] [PATCH] Spill Comments
On Monday 14 September 2009 13:07, Dan Gohman wrote:
> MachineMemOperands for spill slots use FixedStack PseudoSourceValues
> as their base. There's a unique FixedStack PseudoSourceValue for each
> fixed frame object, so it's independent of whether frame pointer
> elimination has been done, and it's independent of the actual frame
> offsets.
>From
2009 Sep 14
0
[LLVMdev] [PATCH] Spill Comments
On Monday 14 September 2009 15:28, David Greene wrote:
> I don't see PseudoSourceValue::FPRel, etc. defined anywhere. How do I know
> if a PseudoSourceValue is from the stack?
Ok, the comment is misleading. I see the class defined in
PseudoSourceValue.cpp now. I'll move it to the header.
I have another question. Looking at the list of MachineMemOperands for an
instruction, is
2011 Aug 06
0
[LLVMdev] How to differ from read and write operations for general stack objects
...d stack objects.
For virtual registers, we could use the MachineOperand::isDef() and
MachineOperand::isUse.
For stack objects used for argument-passing (see mem:ST4[Stack] in the
example) or return-value (see mem:ST4[FixedStack3]), we could use the
MachineMemOperand::IsLoad() and MachineMemOperand::IsStore().
For general stack objects, like the first and second instructions in the
example, is there a way for me to identify whether fi#2 is read or written?
--
Best regards,
Li Qing-An
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/l...
2004 Oct 11
0
LLVM October Status Update
...cific stack locations.
20. Alkis contributed several improvements to the linear scan register
allocator, making it run faster and produce better code.
21. Jeff Cohen contributed a patch to the X86 backend to make better use
of complex addressing modes.
22. Nate added support for isLoad/isStore flags to target .td files.
23. The register allocator interface now uses a new spiller (-spiller=local)
which produces substantially better code on X86 with linear scan in
some cases (and is faster than the old one).
Optimizer Changes:
24. The -constifier pass was renamed to -globalop...
2020 Sep 07
2
Change prototype for TargetInstrInfo::foldMemoryOperandImpl
Hi,
While working on https://reviews.llvm.org/D79785, we wanted to define
foldMemoryOperandImpl hook for Thumb1, that folds load, indirect call
to direct call tLDRpci, tBLX -> tBL. This triggered an assertion
error with expensive checks turned on in MachineVerifier because the
newly created tBL insn by
Thumb1InstrInfo::foldMemoryOperandImpl had memory operands of LoadMI
attached by