similar to: [LLVMdev] Tiny machine...

I missed two files from the LLVM source code proper. These need reviewing and commiting. They are trivial changes that should not influence any other builds. Basically these functions are missing a return statement which 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

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 allocating its own variables? - Volodya

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 used by function for

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 stack

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

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

Thank you... I am preparing to build a simple C compiler for our new architecture. According to your suggestion. I try to dynamically load my backend. But I got the error message : llc : target 'Your_Arch' does not support static compilation! could you tell me where is this problem? On Mon, 24 Jan 2005 22:53:15 -0600 (CST), Chris Lattner <sabre at nondot.org> wrote: > On

hello... I have finish my backend. But I dont know how to install my backend... llc -load=???Load what?? Can anyone teach me? thanx.

Howdy everybody. I'm trying hard to load my backend. But I got problems. I took the target SparcV8 for lab. 1. mark all of the code in the bool SparcV8TargetMachine::addPassesToEmitAssembly(PassManager &PM,std::ostream &Out) and make it return false.( Of course I mark the // Output assembly language. PM.add(createSparcV8CodePrinterPass(Out, *this));) 2. generate the

I have got the latest CVS release of LLVM. And built the Win32 MS VC++ 2003 port with modifications for MS VC++ 2005. Do bear in mind the Visual Studio ports are by no means complete, and are on going. Microsoft Visual Studio 2005 Beta (codename Whidbey) can be got from Microsoft Beta program nearly for free; the cost of postage from :-

On Thu, Feb 17, 2005 at 08:41:41PM -0000, Aaron Gray wrote: > I missed two files from the LLVM source code proper. These need > reviewing and commiting. They are trivial changes that should not > influence any other builds. Basically these functions are missing a > return statement which Visual Studio 2005 Beta flags as an error > rather than as a warning. I have put in dummy

On Tue, 25 Jan 2005, s88 wrote: > Thank you... > I am preparing to build a simple C compiler for our new architecture. > According to your suggestion. I try to dynamically load my backend. > But I got the error message : > llc : target 'Your_Arch' does not support static compilation! > could you tell me where is this problem? A useful tool in llvm is named

Hi, I am trying to read the "credit.lisp" file of the Japanese credit database in UCI repository, but it is in lisp format which I do not know how to read. I have not found how to do that in the foreign library http://archive.ics.uci.edu/ml/datasets/Japanese+Credit+Screening <http://archive.ics.uci.edu/ml/datasets/Japanese+Credit+Screening> Could anyone help me? Best

On Tue, 25 Jan 2005, s88 wrote: > hello... > I have finish my backend. But I dont know how to install my backend... > llc -load=???Load what?? > Can anyone teach me? > thanx. There are two ways to do this. You can either link the backend directly into llc (like the X86 or PowerPC backends, see tools/llc/Makefile), or you can dynamically load the backend. To dynamically load

Hi, I'm looking for some pointers on how to troubleshoot this problem. I'm trying to write a backend for the AVR. There is an undefined reference at line 48 which is the line FrameInfo() is on. I've tried to use the MSP430 and other targets as references so I'm not sure what changes I did would cause a problem on this line? AVRTargetMachine::AVRTargetMachine(const Target &T,

Hi! I started writing a LLVM backend for a custom architecture. I have some register and instruction .td files and some other files/classes like a MCStreamer for assembler output. At the moment I can compile some empty programs so far. I implemented the method ::eliminateFrameIndex() similar to the Sparc and ARM backend. The method looks like this: // frame pointer is in reg of class

On Dec 10, 2007, at 9:52 AM, Nicolas Geoffray wrote: > 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 :) Very nice! I don't know enough about EH, someone else

Dear, I have been going through the Targets registered with llvm. As I was looking around, I found an include statement in the file XXXRegisterInfo.h (XXX is any target), #include "llvm/Target/TargetRegisterInfo.h" The question is there is no folder called Target in my llvm directory (file TargetRegistorInfo.h missing ) and still programs compile in the XXX architecture. I want access

Looks sane. Thanks. Evan On Feb 1, 2008, at 1:24 AM, Nicolas Geoffray wrote: > 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 > Index:

I'm trying to add support for inline assembly and I keep getting this error: <jal> "<inline asm>:1:2: error: invalid instruction" which is due to the fact that MatchInstructionImpl() returns Match_MnemonicFail. This function is tablegen'ed in XXXGenAsmMatcher.inc and for some reason it can't find JAL even though I can clearly see it in both MatchTable0[] and