search for: machinejumptableinfo

Displaying 20 results from an estimated 37 matches for "machinejumptableinfo".

2006 Dec 14
1
[LLVMdev] MachineFunction.cpp!!!
.../lib/CodeGen/MachineFunction.cpp: In constructor 'llvm::MachineFunction::MachineFunction(const llvm::Function*, const llvm::TargetMachine&)': /Volumes/data/Wendling/llvm-submission/build/obj/src/llvm/lib/CodeGen/MachineFunction.cpp:127: error: no matching function for call to 'llvm::MachineJumpTableInfo::MachineJumpTableInfo(unsigned int&, unsigned int&)' /Volumes/data/Wendling/llvm-submission/build/obj/src/llvm/include/llvm/CodeGen/MachineJumpTableInfo.h:45: note: candidates are: llvm::MachineJumpTableInfo::MachineJumpTableInfo(const llvm::TargetData*, unsigned int) <near match>...
2009 May 12
1
[LLVMdev] MachineJumpTableInfo.h Warning
Another warning: r:\sdks\llvm\trunk\lib\target\x86\asmprinter\X86ATTAsmPrinter.h(29) : warning C4099: 'llvm::MachineJumpTableInfo' : type name first seen using 'class' now seen using 'struct' R:\SDKs\llvm\trunk\include\llvm/CodeGen/MachineFunction.h(34) : see declaration of 'llvm::MachineJumpTableInfo' The problem appears to be in file MachineJumpTableInfo.h on line 29: struct MachineJump...
2008 Mar 30
3
[LLVMdev] Being able to know the jitted code-size before emitting
Hi everyone, vmkit requires to know the size of a jitted method before emitting the method. This allows to allocate the correct size for the method. The attached patch creates this functionality when the flag SizedMemoryCode is on. In order to implement this functionality, i had to virtualize some MachineCodeEmitter functions. Is it OK to commit the patch? Thanks, Nicolas --------------
2008 Nov 13
0
[LLVMdev] 'struct' now seen using 'class'
...guage' : type name first seen using 'class' now seen using 'struct' 14> C:\llvm\include\llvm/Debugger/ProgramInfo.h(33) : see declaration of 'llvm::SourceLanguage' 16>c:\dj\llvm\lib\target\x86\asmprinter\X86ATTAsmPrinter.h(29) : warning C4099: 'llvm::MachineJumpTableInfo' : type name first seen using 'class' now seen using 'struct' 16> C:\llvm\include\llvm/CodeGen/MachineFunction.h(34) : see declaration of 'llvm::MachineJumpTableInfo' 16>c:\dj\llvm\lib\target\x86\asmprinter\X86ATTAsmPrinter.h(29) : warning C4099: 'll...
2008 Apr 01
2
[LLVMdev] Being able to know the jitted code-size before emitting
...ter, which is >> + /// used to output functions to memory for execution. >> +class SizeEmitter : public MachineCodeEmitter { >> + MachineFunction * Fn; >> + void* ConstantPoolBase; >> + void* JumpTableBase; >> + MachineConstantPool *ConstantPool; >> + MachineJumpTableInfo *JumpTable; >> + std::vector<intptr_t> LabelLocations; >> + MachineCodeEmitter* MCE; >> + >> +public: >> + SizeEmitter(MachineCodeEmitter* mce) { >> + CurBufferPtr = 0; >> + BufferBegin = 0; >> + BufferEnd = (unsigned char*)-1; >&...
2008 Mar 31
0
[LLVMdev] Being able to know the jitted code-size before emitting
...f the > MachineCodeEmitter, which is > + /// used to output functions to memory for execution. > +class SizeEmitter : public MachineCodeEmitter { > + MachineFunction * Fn; > + void* ConstantPoolBase; > + void* JumpTableBase; > + MachineConstantPool *ConstantPool; > + MachineJumpTableInfo *JumpTable; > + std::vector<intptr_t> LabelLocations; > + MachineCodeEmitter* MCE; > + > +public: > + SizeEmitter(MachineCodeEmitter* mce) { > + CurBufferPtr = 0; > + BufferBegin = 0; > + BufferEnd = (unsigned char*)-1; > + MCE = mce; > + } > +...
2008 Apr 01
0
[LLVMdev] Being able to know the jitted code-size before emitting
.../// used to output functions to memory for execution. >>> +class SizeEmitter : public MachineCodeEmitter { >>> + MachineFunction * Fn; >>> + void* ConstantPoolBase; >>> + void* JumpTableBase; >>> + MachineConstantPool *ConstantPool; >>> + MachineJumpTableInfo *JumpTable; >>> + std::vector<intptr_t> LabelLocations; >>> + MachineCodeEmitter* MCE; >>> + >>> +public: >>> + SizeEmitter(MachineCodeEmitter* mce) { >>> + CurBufferPtr = 0; >>> + BufferBegin = 0; >>> + Buffe...
2008 Apr 04
3
[LLVMdev] Being able to know the jitted code-size before emitting
...ctions to memory for execution. >>>> +class SizeEmitter : public MachineCodeEmitter { >>>> + MachineFunction * Fn; >>>> + void* ConstantPoolBase; >>>> + void* JumpTableBase; >>>> + MachineConstantPool *ConstantPool; >>>> + MachineJumpTableInfo *JumpTable; >>>> + std::vector<intptr_t> LabelLocations; >>>> + MachineCodeEmitter* MCE; >>>> + >>>> +public: >>>> + SizeEmitter(MachineCodeEmitter* mce) { >>>> + CurBufferPtr = 0; >>>> + BufferBegin...
2008 Apr 05
2
[LLVMdev] Being able to know the jitted code-size before emitting
...>> +class SizeEmitter : public MachineCodeEmitter { >>>>>> + MachineFunction * Fn; >>>>>> + void* ConstantPoolBase; >>>>>> + void* JumpTableBase; >>>>>> + MachineConstantPool *ConstantPool; >>>>>> + MachineJumpTableInfo *JumpTable; >>>>>> + std::vector<intptr_t> LabelLocations; >>>>>> + MachineCodeEmitter* MCE; >>>>>> + >>>>>> +public: >>>>>> + SizeEmitter(MachineCodeEmitter* mce) { >>>>>> + CurB...
2008 Apr 05
0
[LLVMdev] Being able to know the jitted code-size before emitting
...Emitter : public MachineCodeEmitter { >>>>>>> + MachineFunction * Fn; >>>>>>> + void* ConstantPoolBase; >>>>>>> + void* JumpTableBase; >>>>>>> + MachineConstantPool *ConstantPool; >>>>>>> + MachineJumpTableInfo *JumpTable; >>>>>>> + std::vector<intptr_t> LabelLocations; >>>>>>> + MachineCodeEmitter* MCE; >>>>>>> + >>>>>>> +public: >>>>>>> + SizeEmitter(MachineCodeEmitter* mce) { >>>&g...
2008 Apr 04
0
[LLVMdev] Being able to know the jitted code-size before emitting
...cution. >>>>> +class SizeEmitter : public MachineCodeEmitter { >>>>> + MachineFunction * Fn; >>>>> + void* ConstantPoolBase; >>>>> + void* JumpTableBase; >>>>> + MachineConstantPool *ConstantPool; >>>>> + MachineJumpTableInfo *JumpTable; >>>>> + std::vector<intptr_t> LabelLocations; >>>>> + MachineCodeEmitter* MCE; >>>>> + >>>>> +public: >>>>> + SizeEmitter(MachineCodeEmitter* mce) { >>>>> + CurBufferPtr = 0; >>&g...
2008 Apr 07
2
[LLVMdev] Being able to know the jitted code-size before emitting
...hineCodeEmitter { >>>>>>>> + MachineFunction * Fn; >>>>>>>> + void* ConstantPoolBase; >>>>>>>> + void* JumpTableBase; >>>>>>>> + MachineConstantPool *ConstantPool; >>>>>>>> + MachineJumpTableInfo *JumpTable; >>>>>>>> + std::vector<intptr_t> LabelLocations; >>>>>>>> + MachineCodeEmitter* MCE; >>>>>>>> + >>>>>>>> +public: >>>>>>>> + SizeEmitter(MachineCodeEmitter* m...
2008 Apr 07
0
[LLVMdev] Being able to know the jitted code-size before emitting
...t;>>>>>>>> + MachineFunction * Fn; >>>>>>>>> + void* ConstantPoolBase; >>>>>>>>> + void* JumpTableBase; >>>>>>>>> + MachineConstantPool *ConstantPool; >>>>>>>>> + MachineJumpTableInfo *JumpTable; >>>>>>>>> + std::vector<intptr_t> LabelLocations; >>>>>>>>> + MachineCodeEmitter* MCE; >>>>>>>>> + >>>>>>>>> +public: >>>>>>>>> + SizeEmitter(M...
2010 Mar 02
0
[LLVMdev] Disabling emission of jump table info
...again outside the function after the label .LJTI1_0. The .LJTI1_0 label at the start of the second set of jumptable entries is completely unreferenced. Given that MCAsmInfo is the wrong place would it make sense to describe it instead as a separate type of jump table encoding and add it to the MachineJumpTableInfo::JTEntryKind enum? -- Richard Osborne | XMOS http://www.xmos.com -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: switch.s URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100302/dc46f567/attachment.ksh>
2007 Aug 17
0
[LLVMdev] MBB Critical edges
Sorry about the tardiness of my reply. My mail client has playing tricks with me. :-) I am assuming the issue has nothing to do the branch to jumptable instructions but rather the MachineJumpTableInfo associated with every MachineFunction? If so, please take a look at BranchFoldiing.cpp for an example. Evan On Aug 10, 2007, at 12:30 PM, Fernando Magno Quintao Pereira wrote: > > Hi all, > > I have a pass to break critical edges of Machine Basic Blocks, > but I > jus...
2010 Mar 01
2
[LLVMdev] Disabling emission of jump table info
On Mar 1, 2010, at 10:52 AM, Richard Osborne wrote: > On 23/02/10 14:58, Richard Osborne wrote: >> I've recently changed the XCore target to implement BR_JT as a jump to a >> series jumps. The jump table entries are expand inline in the function >> so there is no longer a need to emit jump tables at the end of the >> function. However the emission of jump tables at
2007 Aug 10
2
[LLVMdev] MBB Critical edges
Hi all, I have a pass to break critical edges of Machine Basic Blocks, but I just discovered a bug (when compiling code for x86). The problem is 'jumpl *%reg'. I don't know how to update the jump table for this type of instruction. The code that I had (see below) does not update the jump table, and the actual branch keeps jumping to the old basic block, instead of the new.
2007 Aug 17
2
[LLVMdev] MBB Critical edges
...th default RA (linearscan) is passing, although I am still using LLVM v1.8. best, Fernando > Sorry about the tardiness of my reply. My mail client has playing > tricks with me. :-) > > I am assuming the issue has nothing to do the branch to jumptable > instructions but rather the MachineJumpTableInfo associated with every > MachineFunction? If so, please take a look at BranchFoldiing.cpp for > an example. > > Evan > > On Aug 10, 2007, at 12:30 PM, Fernando Magno Quintao Pereira wrote: > >> >> Hi all, >> >> I have a pass to break critical edges of...
2014 Sep 02
2
[LLVMdev] Problem linking and JITing code through C++-API
Yes. It appears that a bad reference to DataLayout was passed to MachineJumpTableInfo::getEntrySize. I'm using LLVM as a pre-compiled Ubuntu package for this work, so I can't do much more in GDB without building from source. Program received signal SIGSEGV, Segmentation fault. 0x00000000007565f0 in llvm::MachineJumpTableInfo::getEntrySize(llvm::DataLayout const&) const...
2014 Sep 08
2
[LLVMdev] Problem linking and JITing code through C++-API
...gt; From: Andy Jost [Andrew.Jost at synopsys.com] > Sent: Tuesday, September 02, 2014 4:00 PM > To: Reed Kotler; Andy Jost; LLVMdev at cs.uiuc.edu > Subject: RE: Problem linking and JITing code through C++-API > > Yes. It appears that a bad reference to DataLayout was passed to > MachineJumpTableInfo::getEntrySize. I'm using LLVM as a pre-compiled > Ubuntu package for this work, so I can't do much more in GDB without > building from source. > > Program received signal SIGSEGV, Segmentation fault. > 0x00000000007565f0 in > llvm::MachineJumpTableInfo::getEntrySize(llvm:...