Displaying 8 results from an estimated 8 matches for "bytecodelibs".
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
-------
---
Valery A.Khamenya
2003 Oct 26
0
[LLVMdev] redhat 9, compiling llvm-1.0.tar.gz
...alery 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 it (you have to provide the path to the C
frontend to the configure scri...
2004 Jul 21
0
[LLVMdev] GC questions.
...uint, but maybe I should? Hopefully I've understood
the llvm source correctly.
, Tobias
[1] I'm kind of newbie of cvs, but I did:
"cvs -z3 -d :pserver:anon at llvm-cvs.cs.uiuc.edu:/var/cvs/llvm diff llvm > gcpatch"
-------------- next part --------------
? llvm/l
? llvm/lib/BytecodeLibs
? llvm/lib/Debug
? llvm/lib/Analysis/Debug
? llvm/lib/Analysis/Depend
? llvm/lib/Analysis/DataStructure/Debug
? llvm/lib/Analysis/DataStructure/Depend
? llvm/lib/Analysis/IPA/Debug
? llvm/lib/Analysis/IPA/Depend
? llvm/lib/AsmParser/Debug
? llvm/lib/AsmParser/Depend
? llvm/lib/Bytecode/Reader/Debug...
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 Jul 22
2
[LLVMdev] GC questions.
...hen we
> > get threads (to put safe points in loops and other places that don't have
> > calls). Since field accesses like this are all very short lived, they can
> > all just be registers.
> >
> > -Chris
-------------- next part --------------
? llvm/l
? llvm/lib/BytecodeLibs
? llvm/lib/Debug
? llvm/lib/Analysis/Debug
? llvm/lib/Analysis/Depend
? llvm/lib/Analysis/DataStructure/Debug
? llvm/lib/Analysis/DataStructure/Depend
? llvm/lib/Analysis/IPA/Debug
? llvm/lib/Analysis/IPA/Depend
? llvm/lib/AsmParser/Debug
? llvm/lib/AsmParser/Depend
? llvm/lib/Bytecode/Reader/Debug...
2004 Oct 23
1
[LLVMdev] UPDATE: Makefile.rules Changes (IMPORTANT)
If you're on the new Makefile system, you will want to update your
Makefile.rules. The patch below provides some important fixes for
parallel builds and dependencies. It also adds some new features like
the -local targets. For example, you can now build "all-local" to build
the local directory without recursing into subdirectories.
See the comments below for details of the change.