Displaying 5 results from an estimated 5 matches for "getinlineasmlength".
2008 Dec 10
0
[LLVMdev] ARM Debug support patch
...ments:
1. Please don't use tabs.
2.
Index: lib/Target/ARM/ARMInstrInfo.cpp
===================================================================
--- lib/Target/ARM/ARMInstrInfo.cpp (revision 14)
+++ lib/Target/ARM/ARMInstrInfo.cpp (working copy)
@@ -904,7 +904,8 @@
return TAI->getInlineAsmLength(MI-
>getOperand(0).getSymbolName());
if (MI->isLabel())
return 0;
- if (MI->getOpcode() == TargetInstrInfo::IMPLICIT_DEF)
+ if (MI->getOpcode() == TargetInstrInfo::IMPLICIT_DEF ||
+ MI->getOpcode() == TargetInstrInfo::DECLARE)
return 0;
Sa...
2008 Dec 10
6
[LLVMdev] ARM Debug support patch
Hi all,
FlexyCore, the company I am working for, use LLVM to generate binary for ARM
platform. We are very fulfilled with LLVM, and FlexyCore will be pleased to
contribute on this software.
We need debug support in ARM binary, but, in LLVM 2.4, this support is not
activated for ARM backend. Consequently, I made small modifications in order
to activate it (see the patch in attach file). My
2008 Apr 16
0
[LLVMdev] Being able to know the jitted code-size before emitting
...switch (MI->getOpcode()) {
> - case PPC::INLINEASM: { // Inline Asm: Variable size.
> - MachineFunction *MF = MI->getParent()->getParent();
> - const char *AsmStr = MI->getOperand(0).getSymbolName();
> - return MF->getTarget().getTargetAsmInfo()-
> >getInlineAsmLength(AsmStr);
> - }
> - case PPC::LABEL: {
> - return 0;
> - }
> - default:
> - return 4; // PowerPC instructions are all 4 bytes
> - }
> -}
> -
> -
> bool PPCBSel::runOnMachineFunction(MachineFunction &Fn) {
> const TargetInstrInfo *TII = Fn.getTarge...
2008 Apr 15
4
[LLVMdev] Being able to know the jitted code-size before emitting
OK, here's a new patch that adds the infrastructure and the
implementation for X86, ARM and PPC of GetInstSize and GetFunctionSize.
Both functions are virtual functions defined in TargetInstrInfo.h.
For X86, I moved some commodity functions from X86CodeEmitter to
X86InstrInfo.
What do you think?
Nicolas
Evan Cheng wrote:
>
> I think both of these belong to TargetInstrInfo. And
2011 May 06
0
[LLVMdev] Question about linking llvm-mc when porting a new backend
...rInfo::~EBCGenRegisterInfo()in
libLLVMEBCCodeGen.a(EBCRegisterInfo.cpp.o)
llvm::EBCGenRegisterInfo::~EBCGenRegisterInfo()in
libLLVMEBCCodeGen.a(EBCRegisterInfo.cpp.o)
llvm::EBCGenRegisterInfo::~EBCGenRegisterInfo()in
libLLVMEBCCodeGen.a(EBCInstrInfo.cpp.o)
"llvm::TargetInstrInfo::getInlineAsmLength(char const*, llvm::MCAsmInfo
const&) const", referenced from:
vtable for llvm::EBCInstrInfoin
libLLVMEBCCodeGen.a(EBCTargetMachine.cpp.o)
vtable for llvm::TargetInstrInfoImplin
libLLVMCodeGen.a(TargetInstrInfoImpl.cpp.o)
vtable for llvm::EBCInstrInfoin
libLLVMEBCCodeGen.a...