similar to: [LLVMdev] Can't get llvmg++ to work

Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] Can't get llvmg++ to work"

2004 Aug 19
0
[LLVMdev] Can't get llvmg++ to work
On Wed, 2004-08-18 at 22:14, Jeff Cohen wrote: > I'm another new person to LLVM. Hi Jeff. Welcome. > I can't successfully compile and > execute a simple C++ program. The compiler seems to work, as it > produces a.out and a.out.bc files, but I get a whole bunch of warnings: > > WARNING: Found global types that are not compatible: >
2004 Aug 19
1
[LLVMdev] Can't get llvmg++ to work
On Thu, 19 Aug 2004 08:45:23 -0700 Reid Spencer <reid at x10sys.com> wrote: > > I'm running FreeBSD 5.2.1 with gcc 3.3.3. I had some problem starting > > the build as I had to get linux binary emulation to work. (The problem > > here is that FreeBSD can be made compatible with 5 different distros, > > and not all of them work with LLVM. I used linux_base-8;
2004 Aug 20
2
[LLVMdev] Can't get llvmg++ to work
On Thu, 19 Aug 2004 08:45:23 -0700 Reid Spencer <reid at x10sys.com> wrote: > > Also, as a general note, make sure you follow precisely the steps for > building the c front end. If you discover any BSDisms that aren't > documented, we'd love to hear about them. > > Thanks, > > Reid. > OK. I've built the front end without any heartaches, but I did
2004 Dec 05
1
[LLVMdev] Building llvm and cfrontend under cygwin
Hi there, I'm trying to build llvm under cygwin running under windows xp, and have struck the following problem: -- llvm: tools-only built ok -- cfrontend: built ok -- llvm: full build failed at the following point: make[3]: Entering directory `/cygdrive/d/3rd-party/llvm/runtime/GCCLibraries/crtend' Compiling crtend.c to bytecode Compiling listend.ll to bytecode Linking comp_main.bc
2004 Aug 16
3
[LLVMdev] Re: [llvm-announce] LLVM 1.3 Release!]
Chris Lattner wrote: >On Sun, 15 Aug 2004, Robert Feldt wrote: > > > >>However, I wonder if someone supplies pre-built cfrontend binaries for >>cygwin? >> >> > >Nope, we don't have one yet, sorry. > > > >>I followed the instructions and tried to build them myself but get >>when building the cfrontend. Any ideas? >>
2004 Aug 15
0
[LLVMdev] Re: [llvm-announce] LLVM 1.3 Release!]
On Sun, 15 Aug 2004, Robert Feldt wrote: > However, I wonder if someone supplies pre-built cfrontend binaries for > cygwin? Nope, we don't have one yet, sorry. > I followed the instructions and tried to build them myself but get > when building the cfrontend. Any ideas? That is really wierd. Looking at that line of gcc.c, I have no idea how it ever worked. In any case, this
2004 Aug 15
2
[LLVMdev] Re: [llvm-announce] LLVM 1.3 Release!]
Chris Lattner wrote: > LLVM Compiler Infrastructure -- Release 1.3 > http://llvm.cs.uiuc.edu > >We are pleased to announce the release of version 1.3 of the LLVM >Compiler Infrastructure. > > > Great news, thanks. However, I wonder if someone supplies pre-built cfrontend binaries for cygwin? I followed the instructions and tried to
2004 Aug 16
0
[LLVMdev] Re: [llvm-announce] LLVM 1.3 Release!]
On Mon, Aug 16, 2004 at 01:07:39PM +0200, Robert Feldt wrote: > However, when I go back to rebuild llvm, reconfigure, setting the > CFEINSTALL dir, then make it can build the tools ok but not the > runtime: [snip] > Compiling crtend.c to bytecode > Files/ATI: not found [snip] > I don't understand the error message since I see no reference to > Files/ATI. Any clues? Can
2004 Jul 21
2
[LLVMdev] GC questions.
On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > Hi, I'm thinking out loud, please give me some feedback. > > Regarding llvm.gcread and llvm.gcwrite, wouldn't it be nicer if they are > implemented as: > > llvm.gcread(sbyte** object, uint offset) > llvm.gcwrite(sbyte* data, sbyte** object, uint offset) > > Where you also have the offset into the object. In
2004 Jul 21
0
[LLVMdev] GC questions.
Ok, that makes sense :). , Tobias On Wed, 21 Jul 2004, Chris Lattner wrote: > On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > > void *llvm_gc_read(void *ObjPtr, void **FieldPtr) { > > > return *FieldPtr; > > > } > > > > Hm, but doesn't FieldPtr need to be calculated target-specific in those > > cases? > > For the field pointer, one
2004 Jul 21
2
[LLVMdev] GC questions.
On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > void *llvm_gc_read(void *ObjPtr, void **FieldPtr) { > > return *FieldPtr; > > } > > Hm, but doesn't FieldPtr need to be calculated target-specific in those > cases? For the field pointer, one could use the getelementptr instruction: %pairty = { sbyte, sbyte, int* } %pairPtr = ... %fieldptr = getelementptr
2004 Dec 08
0
[LLVMdev] Building llvm and cfrontend under cygwin
Hi Reid, > 2. Make sure you aren't trying to link in some old/crufty crtend.bc > file. Try doing "make uninstall ; make clean" in your crtend > directory if you think this might be the case. "make install" fails - there is no such target. > If those don't clear the problem, please tell me what version > of LLVM you're trying to compile
2003 Dec 22
2
[LLVMdev] hello.bc & binary code
hi, I try to build hello.cpp using both llvmg++ and GNU g++, the generate llvm bytecode's size is about 960K, and the size of binary code generated by g++ is only 13K. Could anyone explain the difference between the two result? BWT: I rebuild the cfrontend in RH linux9.0, but when I build the hello.cpp the llvmG++ reports warnings too, it shows: ----------------------------- [yue at RH9
2004 Aug 20
0
[LLVMdev] Can't get llvmg++ to work
Hi Jeff, On Fri, 2004-08-20 at 08:07, Jeff Cohen wrote: > OK. I've built the front end without any heartaches, but I did > encountered the following glitches: > > The documentation of --with-llvmgccdir is a bit ambiguous. I had to try > several paths before I got the right one. It should state that the > directory is <path>/cfrontend/<platform>/llvm-gcc.
2004 Dec 10
1
[LLVMdev] Building llvm and cfrontend under cygwin
Hi Chris, > Also note, LLVM 1.4 will be released in the next few days, so if waiting is > an option, you might choose to do so. Alright, I've got llvm and llvm-gcc from RELEASE_14 cvs and tried building it under cygwin. 1) The first problem is with llvm in SysUtils.c: int executeProgram(const char *filename, char *const argv[], char *const envp[]) { ................ execveTy
2003 Oct 26
2
[LLVMdev] redhat 9, compiling llvm-1.0.tar.gz
Hi all, compilation of package llvm-1.0.tar.gz under redhat 9 is failed with following output: ------- make[3]: *** No rule to make target `/home/vak/llvm/llvm/runtime/GCCLibraries/crtend/BytecodeObj/C++-Exception.bc', needed by `/home/vak/llvm/llvm/lib/BytecodeLibs/libcrtend.bc'. Stop. make[3]: Leaving directory `/home/vak/llvm/llvm/runtime/GCCLibraries/crtend' ...skipped -------
2005 Jan 26
3
[LLVMdev] Building the llvm runtime: 'Can't destroy file: The process cannot access the fi
Hi Jeff and others, When building the llvm runtime, I always get this error message: 'Can't destroy file: The process cannot access the file because it is being used by another process.' The file is destoyed anyway. I think that the the real error is the path for the file (*/\file.tmp). However, I can't find the bug in the source. Do you have any clue?:
2006 Aug 21
1
[LLVMdev] stdlib.h
Thank you, Reid, I tried llvm-gcc -lcrtend ary3.c -o ary3, but I get gccld: warning: Cannot find library 'crtend' gccld: warning: Cannot find library 'c' I have the libraries in my llvm directory: llvm/runtime/GCCLibraries/crtend Well, how do I link this to the LLVM runtime stuff? Before building from the source, I had copied all the .h from my old gcc 4.0 to
2005 Jan 26
0
[LLVMdev] Building the llvm runtime: 'Can't destroy file: The process cannot access the fi
It looks like what you're getting is a sharing violation. Although, I don't understand why. The llvm-ar.exe when its building an archive file always builds it in a temporary. Only when that is complete does it remove the old one and rename the temporary. Perhaps this is a result of doing parallel build and the "lib3.tmp" file (that name looks wrong to me) is being accessed by
2006 Aug 20
0
[LLVMdev] stdlib.h
Try adding -lcrtend to the gcc link line. You need to link in the LLVM runtime stuff. Reid. On Sun, 2006-08-20 at 14:30 -0700, Fernando Magno Quintao Pereira wrote: > > Rebuilding llvm-gcc4 from source should work fine. Please see the > > directions in the file README.LLVM at the top level src directory. You > > can check llvm-gcc4 out from Subversion with the command: >