search for: targetframeinfo

...degen\selectiondag\selectiondagisel.cpp(744) : error C4716: 'llvm::TargetLowering::LowerVAArgNext' : must return a value c:\languages\llvm\lib\codegen\selectiondag\selectiondagisel.cpp(792) : error C4716: 'llvm::TargetLowering::LowerOperation' : must return a value \llvm\lib\target\targetframeinfo.cpp ------------------------------------------------- c:\languages\llvm\lib\target\targetframeinfo.cpp(27) : error C4716: 'llvm::TargetFrameInfo::adjustAlignment' : must return a value c:\languages\llvm\lib\target\targetframeinfo.cpp(36) : error C4716: 'llvm::TargetFrameInfo::getIncomi...

...in return statements to allow CodeGen and Target libraries to build. The files :- \llvm\lib\codegen\selectiondag\selectiondagisel.cpp llvm::TargetLowering::LowerVAStart llvm::TargetLowering::LowerVAArgNext llvm::TargetLowering::LowerOperation \llvm\lib\target\targetframeinfo.cpp llvm::TargetFrameInfo::adjustAlignment llvm::TargetFrameInfo::getIncomingArgOffset llvm::TargetFrameInfo::getOutgoingArgOffset llvm::TargetFrameInfo::getFirstAutomaticVarOffset llvm::TargetFrameInfo::getRegSpillAreaOffset llvm::TargetFrameInfo::g...

The TargetFrameInfo, amoung other things, specifies "local area offset" -- which, as comment say, is: the offset of the local area from the stack pointer on entrance to a function. The question is -- what's local area? Is this the first stack location which can be used by function for allocatin...

On Mon, 7 Jun 2004, Vladimir Prus wrote: > > The TargetFrameInfo, amoung other things, specifies "local area offset" -- > which, as comment say, is: > > the offset of the local area from the stack pointer on entrance to a > function. > > The question is -- what's local area? Is this the first stack location which > can be...

Chris Lattner wrote: > On Mon, 7 Jun 2004, Vladimir Prus wrote: > > The TargetFrameInfo, amoung other things, specifies "local area offset" > > -- which, as comment say, is: > > > > the offset of the local area from the stack pointer on entrance to a > > function. > > > > The question is -- what's local area? Is this the first st...

...getMachine(const Target &T, const std::string &TT, const std::string &FS) : LLVMTargetMachine(T, TT), Subtarget(TT, FS), DataLayout("e-p:16:8:8-i8:8:8-i16:8:8-i32:8:8"), InstrInfo(Subtarget), TLInfo(*this), FrameInfo(TargetFrameInfo::StackGrowsDown, 1, 0) { } Linking CXX executable ../../bin/llvm-mc cd /home/john/src/llvm_build/tools/llvm-mc && /usr/bin/cmake -E cmake_link_script CMakeFiles/llvm-mc.dir/link.txt --verbose=1 /usr/bin/c++ -g -fPIC CMakeFiles/llvm-mc.dir/llvm-mc.cpp.o CMakeFiles/llvm-mc.dir/AsmExpr....

The X86 backend has this code: X86TargetMachine::X86TargetMachine(const Module &M, IntrinsicLowering *IL) : .... FrameInfo(TargetFrameInfo::StackGrowsDown, 8/*16 for SSE*/, 4), That is, it uses "4" as local area offset. Based on prior discussion this should mean that the local area starts and address ESP+4. Is this really true? On X86 stack grows down, so I'd expect local area to start below ESP, e.g. at ESP - 4, and...

On Wed, 9 Jun 2004, Vladimir Prus wrote: > > The X86 backend has this code: > > X86TargetMachine::X86TargetMachine(const Module &M, IntrinsicLowering *IL) > : .... > FrameInfo(TargetFrameInfo::StackGrowsDown, 8/*16 for SSE*/, 4), > > That is, it uses "4" as local area offset. Based on prior discussion this > should mean that the local area starts and address ESP+4. Is this really > true? On X86 stack grows down, so I'd expect local area to start below ESP, >...

Hello... I have a very simple and tiny processor. It doesn't support procedule call. Do I still need to add the code about TargetFrameInfo and implement the stack operations in the XXXRegisterInfo.cpp????? Thanx. Dave.

...ch Visual Studio 2005 Beta flags as an error > rather than as a warning. I have put in dummy constructors in return > statements to allow CodeGen and Target libraries to build. > > The files :- > > \llvm\lib\codegen\selectiondag\selectiondagisel.cpp > \llvm\lib\target\targetframeinfo.cpp Thanks for the patches! Commits here: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20050214/024164.html http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20050214/024165.html -- Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu

.../ExecutionEngine/GenericValue.h" > #include "llvm/ExecutionEngine/JITMemoryManager.h" > +#include "llvm/Target/MRegisterInfo.h" > +#include "llvm/Target/TargetAsmInfo.h" > #include "llvm/Target/TargetData.h" > +#include "llvm/Target/TargetFrameInfo.h" > +#include "llvm/Target/TargetInstrInfo.h" > #include "llvm/Target/TargetJITInfo.h" > #include "llvm/Target/TargetMachine.h" > +#include "llvm/Target/TargetOptions.h" > #include "llvm/Support/Debug.h" > #include "...

Hi everyone, Here's a patch that enables exception handling when jitting. I've copy/pasted _many_code from lib/Codegen/DwarfWriter.cpp, so we may need to factorize it, but the functionality is there and I'm very happy with it :) lli should now be able to execute the output from llvm-gcc when using exceptions (the UnwindInst instruction is not involved in this patch). Just add the

...t;llvm/ExecutionEngine/JITMemoryManager.h" > +#include "llvm/Target/MRegisterInfo.h" > +#include "llvm/Target/TargetAsmInfo.h" > +#include "llvm/Target/TargetData.h" > +#include "llvm/Target/TargetInstrInfo.h" > +#include "llvm/Target/TargetFrameInfo.h" > +#include "llvm/Target/TargetMachine.h" > + > +using namespace llvm; > + > +JITDwarfEmitter::JITDwarfEmitter(JIT& theJit) : Jit(theJit) {} > + > + > +unsigned char* JITDwarfEmitter::EmitDwarfTable(MachineFunction& F, > +...

Dear all, Here's a new patch with Evan's comments (thx Evan!) and some cleanups. Now the (duplicated) exception handling code is in a new file: lib/ExecutionEngine/JIT/JITDwarfEmitter. This patch should work on linux/x86 and linux/ppc (tested). Nicolas -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: jit-exceptions.patch URL:

Thx again Evan for the review. Here's a new patch for the JIT in itself. The major changes are: 1) A JITMemoryManager now has a flag saying "I require to know the size of what you want to emit" 2) DwarfJITEmitter is augmented with GetSize* functions 3) JITEmitter::startFunction checks if the JITMemoryManager requires to know the size. If so, it computes it and gives it through the

...ess-exposed automatic variables. 20. X86: Other minor code quality improvements. 21. The C backend now emits syntactic loops in the output .c file, in order to get decent code quality from C compilers that do not handle gotos well (like GCC). 22. Vladimir Prus contributed changes to the TargetFrameInfo class to make it work for targets whose stack grows up as well as down in memory. 23. The TargetMachine class is now cleaner and more regular. Miscellaneous Changes: 24. Reid added regression and feature testing to the nightly tester. 25. Tanya and Misha found and fixed all broken links on th...

Paolo Invernizzi wrote: > There was a similar problem some time ago, and was resolved with alloca. > I think it's a better solution to use the stack instead of the heap... I tend to agree, but the constructors won't get called if it's an object array -- anyway, this particular case there was no objects, just pointers and bools so alloca should be fine. I'll leave it to

...rror: 'uint64_t' has not been declared /usr/src/Lang/llvm/include/llvm/CodeGen/MachineFrameInfo.h:380: error: 'std::ostream' has not been declared /usr/src/Lang/llvm/include/llvm/CodeGen/MachineFrameInfo.h: In constructor 'llvm::MachineFrameInfo::MachineFrameInfo(const llvm::TargetFrameInfo&)': /usr/src/Lang/llvm/include/llvm/CodeGen/MachineFrameInfo.h:173: error: 'StackSize' was not declared in this scope /usr/src/Lang/llvm/include/llvm/CodeGen/MachineFrameInfo.h: In member function 'void llvm::MachineFrameInfo::setObjectSize(int, int)': /usr/src/Lang/llvm/i...

...ericValue.h" >> #include "llvm/ExecutionEngine/JITMemoryManager.h" >> +#include "llvm/Target/MRegisterInfo.h" >> +#include "llvm/Target/TargetAsmInfo.h" >> #include "llvm/Target/TargetData.h" >> +#include "llvm/Target/TargetFrameInfo.h" >> +#include "llvm/Target/TargetInstrInfo.h" >> #include "llvm/Target/TargetJITInfo.h" >> #include "llvm/Target/TargetMachine.h" >> +#include "llvm/Target/TargetOptions.h" >> #include "llvm/Support/Debug.h" &...

.../LiveVariables.h Index: include/llvm/CodeGen/MachineFunction.h Index: include/llvm/CodeGen/MachineInstr.h Index: include/llvm/CodeGen/SchedGraphCommon.h Index: include/llvm/Config/alloca.h Index: include/llvm/Support/Annotation.h Index: include/llvm/Target/MRegisterInfo.h Index: include/llvm/Target/TargetFrameInfo.h Index: include/llvm/Target/TargetInstrInfo.h Index: include/llvm/Target/TargetSchedInfo.h Index: lib/Analysis/Expressions.cpp Index: lib/Analysis/IntervalPartition.cpp Index: lib/Analysis/LoopInfo.cpp Index: lib/Analysis/PostDominators.cpp Index: lib/Analysis/DataStructure/EquivClassGraphs.cpp In...