search for: bytecodeobj

...? llvm/projects/sample/config.status ? llvm/projects/sample/lib/Debug ? llvm/projects/sample/lib/sample/Debug ? llvm/projects/sample/lib/sample/Depend ? llvm/projects/sample/tools/Debug ? llvm/projects/sample/tools/sample/Debug ? llvm/projects/sample/tools/sample/Depend ? llvm/runtime/GC/SemiSpace/BytecodeObj ? llvm/runtime/GC/SemiSpace/Debug ? llvm/runtime/GC/SemiSpace/Depend ? llvm/runtime/GCCLibraries/crtend/BytecodeObj ? llvm/runtime/GCCLibraries/crtend/Depend ? llvm/runtime/GCCLibraries/libc/BytecodeObj ? llvm/runtime/GCCLibraries/libc/Depend ? llvm/runtime/GCCLibraries/libcurses/BytecodeObj ? llvm...

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

...d/Depend/crtend.d make[2]: Leaving directory `/cygdrive/d/3rd-party/llvm/runtime/GCCLibraries/crtend' make[2]: Entering directory `/cygdrive/d/3rd-party/llvm/runtime/GCCLibraries/crtend' /cygdrive/d/3rd-party/llvm/autoconf/mkinstalldirs /cygdrive/d/3rd-party/llvm/runtime/GCCLibraries/crtend/BytecodeObj > /dev/null Compiling crtend.c to bytecode PATH=/cygdrive/d/3rd-party/llvm/tools/Debug:/cygdrive/d/3rd-party/llvm/t ools/Debug:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin /cygdrive/d/3rd-party/cfrontend/install/bin/gcc -Wall -W -Wwrite-strings -Wno-unused -I/cygdrive/d/3rd-party/llvm/runtime/GCC...

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

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

...? llvm/projects/sample/config.status ? llvm/projects/sample/lib/Debug ? llvm/projects/sample/lib/sample/Debug ? llvm/projects/sample/lib/sample/Depend ? llvm/projects/sample/tools/Debug ? llvm/projects/sample/tools/sample/Debug ? llvm/projects/sample/tools/sample/Depend ? llvm/runtime/GC/SemiSpace/BytecodeObj ? llvm/runtime/GC/SemiSpace/Debug ? llvm/runtime/GC/SemiSpace/Depend ? llvm/runtime/GCCLibraries/crtend/BytecodeObj ? llvm/runtime/GCCLibraries/crtend/Depend ? llvm/runtime/GCCLibraries/libc/BytecodeObj ? llvm/runtime/GCCLibraries/libc/Depend ? llvm/runtime/GCCLibraries/libcurses/BytecodeObj ? llvm...

...ory `/cygdrive/d/3rd-party/llvm/runtime/GCCLibraries/crtend' Compiling crtend.c to bytecode Compiling listend.ll to bytecode Linking comp_main.bc component... /cygdrive/d/3rd-party/llvm/tools/Debug/gccld: Error linking in bytecode file '/cygdrive/d/3rd-party/llvm/runtime/GCCLibraries/crtend/BytecodeObj/crte nd.bc': Bytecode file '/cygdrive/d/3rd-party/llvm/runtime/GCCLibraries/crtend/BytecodeObj/crte nd.bc' could not be loaded: Invalid Top Level Block Length! Type:1, Size:880 (Vers=16, Pos=12) make[3]: *** [/cygdrive/d/3rd-party/llvm/runtime/GCCLibraries/crtend/BytecodeObj/comp _main....

...igured it was a good idea to throw away any part of the runtime that did compile successfully, so I "cd runtime" and did a "gmake clean". This apparently deleted too many files, as I then got: gmake[3]: *** No rule to make target `/usr/home/llvm/obj/runtime/GCCLibraries/crtend/BytecodeObj/crtend.bc', needed by `/usr/home/llvm/obj/runtime/GCCLibraries/crtend/BytecodeObj/comp_main.bc'. Stop. Rerunning configure cured the problem. But that touched something that triggers a lot of recompilation. Alas the machine I'm using is underpowered and it'll be a while before i...

...lvm/../../../../include/c++/3.4-llvm/cstdlib:52, > from /usr/home/llvm/obj/../runtime/GCCLibraries/crtend/SJLJ-Exception.cpp:16: > /usr/include/machine/_types.h:88: error: declaration does not declare anything > gmake[3]: *** [/usr/home/llvm/obj/runtime/GCCLibraries/crtend/BytecodeObj/SJLJ-Exception.bc] Error 1 > gmake[3]: Target `all' not remade because of errors. > gmake[3]: Leaving directory `/usr/home/llvm/obj/runtime/GCCLibraries/crtend' > gmake[2]: *** [crtend/.makeall] Error 2 Ah, yeah, that would do it. You have an error making the C Runtime library. Th...

...linux-gnu/3.4-llvm/../../../../include/c++/3.4-llvm/cstdlib:52, from /usr/home/llvm/obj/../runtime/GCCLibraries/crtend/SJLJ-Exception.cpp:16: /usr/include/machine/_types.h:88: error: declaration does not declare anything gmake[3]: *** [/usr/home/llvm/obj/runtime/GCCLibraries/crtend/BytecodeObj/SJLJ-Exception.bc] Error 1 gmake[3]: Target `all' not remade because of errors. gmake[3]: Leaving directory `/usr/home/llvm/obj/runtime/GCCLibraries/crtend' gmake[2]: *** [crtend/.makeall] Error 2

...y `/usr/pd/llvm/llvm/runtime' make[2]: Entering directory `/usr/pd/llvm/llvm/runtime/GCCLibraries' make[3]: Entering directory `/usr/pd/llvm/llvm/runtime/GCCLibraries/crtend' Compiling crtend.c to bytecode Files/ATI: not found make[3]: *** [/usr/pd/llvm/llvm/runtime/GCCLibraries/crtend/BytecodeObj/crtend.b c] Error 127 make[3]: Leaving directory `/usr/pd/llvm/llvm/runtime/GCCLibraries/crtend' make[2]: *** [crtend/.makeall] Error 2 make[2]: Leaving directory `/usr/pd/llvm/llvm/runtime/GCCLibraries' make[1]: *** [GCCLibraries/.makeall] Error 2 make[1]: Leaving directory `/usr/pd/llvm/l...

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 ------- --- Valery A.Khamenya

> Only thing I can think of is that your "platform" link is missing. > make sure "platform is a symbolic link to your platform's subdirectory > in the llvm/lib/System directory. If you're on FreeBSD then: > > ln -s FreeBSD platform > > this should have been done for you when you configured. My fault. I make cvs update llvm and AFTER remove build

...oks like your crtend.a file did not get built correctly. Try doing > > make clean/make install in llvm/runtime/ again. > > lib\Debug\libcrtend.a builded. > > But i not found it in LLVM installation dir after install. 'make install' should install this into the CFRONTEND/bytecodeobjs directory. -Chris -- http://llvm.org/ http://nondot.org/sabre/

...vm/llvm/ runtime/GCCLibraries/crtend -I/usr/pd/llvm/llvm/include -I/usr/pd/llvm/llvm/incl ude -I../../../include -I/usr/pd/llvm/llvm/include -D_GNU_SOURCE -D__STDC_LIMIT_ MACROS -DATTR_DEPRECATED='__attribute__ ((deprecated))' -c crtend.c -o /usr/pd/l lvm/llvm/runtime/GCCLibraries/crtend/BytecodeObj/crtend.bc Files/ATI: not found gmake: *** [/usr/pd/llvm/llvm/runtime/GCCLibraries/crtend/BytecodeObj/crtend.bc] Error 127 So I excluded all the windows-specific dirs in PATH and rebuilt and it went ok. So it does not seem to be enough to build in dirs with no spaces. To build llvm on cygwin yo...

...idea to throw away any part of the runtime that > did compile successfully, so I "cd runtime" and did a "gmake clean". > This apparently deleted too many files, as I then got: > > gmake[3]: *** No rule to make target `/usr/home/llvm/obj/runtime/GCCLibraries/crtend/BytecodeObj/crtend.bc', needed by `/usr/home/llvm/obj/runtime/GCCLibraries/crtend/BytecodeObj/comp_main.bc'. Stop. > > Rerunning configure cured the problem. But that touched something that > triggers a lot of recompilation. Yeah, that can be a pain. > Alas the machine I'm using...

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

...platforms. If you look at runtime/GC/SemiSpace: those files are not compiled using the compiler used to compile the rest of the project (llc, lli and so on). They use the llvm-gcc-frontend to compile and link those libraries into llvm bytecode. The resulting files end up in runtime/GC/SemiSpace/BytecodeObj > > 2. The entire llvm-test project would have to either be completely > > rethought or stay the way it is, it just can't be easily automake'd > > because it doesn't follow the automake pattern. > > > > 3. The llvm/test directory would require significant...

On Sun, 26 Oct 2003, [koi8-r] "Valery A.Khamenya[koi8-r] " wrote: > 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 Makes sure that you have the C front-end installed correctly, and that the configure script found i...

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