similar to: [LLVMdev] open source multithreaded garbage collector suitable for LLVM applications?

Basile STARYNKEVITCH wrote: > Does any know about some opensource multithread-compatible (or > concurrent) garbage collector library, if possible suitable for LLVM? > > (I mean that I want several mutator threads; the collector can be > stoptheworld or concurrent ....) > > H.Boehm's conservative GC is multithread compatible, but seems quite > slow (allocation is

On May 1, 2009, at 1:27 PM, Basile STARYNKEVITCH wrote: > Hello All > > Does any know about some opensource multithread-compatible (or > concurrent) garbage collector library, if possible suitable for LLVM? In fact, yes! http://code.google.com/p/scarcity/ -Chris

Hello All, On a Debian/AMD64 host I am surprised that there is apparently no way to generate position independent code in shared object (i.e. to output files which are easy dlopen-able without pain)? I probably missed something obvious, but what? I want to compile LLVM assembly source code -suitably generated- into .so as directly as possible... Regards -- Basile STARYNKEVITCH

Hello (my machine is a Debian/Sid/x86-64/Core2) Assuming I have one C source file chello.c, to compile it into a dynamically loadable thru dlopen shared object, I can run gcc -fPIC -shared -O chello.c -o chello.so I thought that, assuming I have one llvm source ehello.ll, the equivalent would be llvmc2 -opt ehello.ll -o ehello.so but it is not that simple. Any clues ? May I also

Chris Lattner wrote: > On Mon, 22 Oct 2007, Basile STARYNKEVITCH wrote: >> On a Debian/AMD64 host I am surprised that there is apparently no way to >> generate position independent code in shared object (i.e. to output >> files which are easy dlopen-able without pain)? >> >> I probably missed something obvious, but what? > > You're missing the fact that

On Mon, 22 Oct 2007, Basile STARYNKEVITCH wrote: > On a Debian/AMD64 host I am surprised that there is apparently no way to > generate position independent code in shared object (i.e. to output > files which are easy dlopen-able without pain)? > > I probably missed something obvious, but what? You're missing the fact that llvmc is highly experimental, and is not really usable

Hello All, I suspect that LLVM performs very well, mostly because I respect a lot his main architect Chris. However, I have no ideas about concrete performance of the LLVM compiler, in particular speed of the compilation process to achieve small optimisation (mostly something equivalent to gcc -fPIC -O1 in terms of code quality). The intent is to generated .so files (I want to avoid the

Le Tue, May 08, 2007 at 10:17:41PM -0700, Tanya M. Lattner écrivait/wrote: > > Here is the schedule: > > May 7th - Release branch created. Developers should begin reviewing > all documentation. > > May 14th - Tar balls and binaries are released for general testing. I'll > also need volunteers to create additional llvm-gcc binaries that I have > not provided.

Thank you for this reply. If so, is there any way to merge basic blocks into a single one? Thanks, Seung J. Lee ---- Original message ---- >Date: Fri, 29 Jun 2007 22:27:38 +0200 >From: Basile STARYNKEVITCH <basile at starynkevitch.net> >Subject: Re: [LLVMdev] LLVM assembly without basic block >To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > >Seung

Hello All, What version of g++ is usable to compile the latest LLVM CVS snapshot on a Linux/x86-64 (AMD64) Debian/ Sid or Etch plateform? What compiler do LLVM dzevelopers use to compile LLVM on Linux/X86-64 systems? IKt seems that most versions of g++ fail to compile LLVM and that some others compile it wrongly (producing buggy code)? Why can't g++-4.1 be used? FWIW, the latest gcc

Le Thu, May 03, 2007 at 09:36:22AM -0700, Chris Lattner écrivait/wrote: > On Thu, 3 May 2007, Basile STARYNKEVITCH wrote: > > > > > FWIW, the latest gcc snapshot from yesterday gcc version 4.3.0 20070501 > > (experimental) fail to compile latest LLVM (with compile errors!). > > Please file an llvm bug report with these errors. It may be that we are > doing

Hello, with the latest LLVM (almost 2.0 CVS) what is the right way to read a module from a byte array fetched from a database? I thought that I could subclass llbm::module to add my own fields (typically, a MySQL id number) and then parse it as bitcode, but I am stuck, since apparently the only way to parse bitcode is to use a BitcodeReader then calling materializeModule gives a fresh llvm

Chris Lattner wrote: > On Mon, 5 Nov 2007, Vikram S. Adve wrote: >> -- It would be helpful to add some navigation links at the top and bottom of >> the pages. > > I added a TOC to each chapter, thanks. May I also suggest adding to each HTML page a link to the topmost http://llvm.org/docs/tutorial/ -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email:

Hello All, Is some documentation (e.g. http://llvm.org/docs/LangRef.html) available in printable friendly format like PDF or PostScript or DVI? Regards. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359 8, rue de la Faiencerie, 92340 Bourg La Reine, France *** opinions {are only mines, sont seulement les

Hello All Where is the documentation for ADT/StringMap.h (given into account that I am not quite familiar with stdc++ library)? In particular, I am surprised that key strings are specified by their start and end, I was expecting C-like strings, ie null terminated array of chars. Regards. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email:

Thank you for reminding me the notion of the basic block. Of course, I know all the assembly takes the form of BBs and is divided into units of BB. OK. It looks better for me to explain what I wanted to do more clear from the first. Actually, I am working on emitting out an assembly of VM by using LLVM. LLVM assembly looks similar with this VM assembly except BB. The VM assembly does not have the

Hello All, (Sorry, I probably did already ask something similar before, but I cannot recall it easily) First, I don't understand what precisely is in the /usr/local/include/llvm/Support/ directory In particular, it seems to me that nothing in the documentation says that MemoryBuffer.h in inside it.... I'm quite annoyed to understand what exactly is the public interface to LLVM! The

Dear All, according to http://llvm.org/SVNMigration.html the repository migrated to SubVersion (svn) on june 5th 2007 (almost 10 days ago). Did the migration happened as expected? http://llvm.org/releases/ still mention CVS, and nothing on http://llvm.org/docs/GettingStarted.html#checkout suggest to switch to svn instead of cvs. What is the current best way to download the latest snapshot:

>> Apparently BitcodeReader.h is only in lib/Bitcode/Reader/ but not in >> include, so a make install does not install it. >I'm not sure what you mean... the header is in include/llvm/Bitcode. >> Is it supposed to be accessible from applications? How exactly? I feel that >> some install rule is missing; after a sudo make install, >> grep -rn BitcodeReader

On Sat, 12 May 2007, Basile STARYNKEVITCH wrote: > with the latest LLVM (almost 2.0 CVS) what is the right way to read a module > from a byte array fetched from a database? The bitcode reader will read from any MemoryBuffer object. There are a variety of static methods on MemoryBuffer to create them from files, stdio, and memory. If your buffer is in memory, just create a memorybuffer