similar to: [LLVMdev] New HLVM examples

I have been working on a high-level virtual machine built upon LLVM since Christmas 2008 and just released the first working version: http://forge.ocamlcore.org/projects/hlvm/ This alpha release of HLVM provides: . Unit, bool, int and float primitive types. . Tuples (as first-class structs). . Homogeneous array type. . Boxed value type. . Function pointers. . Generic printing. . Full tail

I have committed the changes to HLVM that bring it up to date with respect to the new LLVM 2.6 release: http://hlvm.forge.ocamlcore.org/ This required handling of llcontexts and the injection of a call to the new Llvm_executionengine.initialize_native_target function (that is undocumented) *before* the JIT EE is created, otherwise LLVM resorts to the LLVM interpreter which breaks at

All, Chris Lattner and I had a recent discussion about merging the HLVM (http://hlvm.org/) and LLVM (http://llvm.org/) projects. We agreed in principle and the merging of the two projects will now commence. This merger makes sense for both projects. LLVM needs to expand into the realm of front end tool kits. HLVM provides LLVM with some initial front-end capabilities. Since HLVM uses LLVM and

Following on from the success of our previous OCaml Journal articles covering LLVM, we have begun a series dedicated to the design and implementation of high-level languages using LLVM. In particular, these new articles are more pragmatic in nature and go beyond describing working compilers to also discuss testing, debugging and the performance of LLVM-based compilers. The first article in

I'd love to read this article, but I can't justify paying to register. Will it become a 'freely available' article at any point soon? Thanks On Jan 25, 2009, at 7:16 AM, Jon Harrop wrote: > > Following on from the success of our previous OCaml Journal articles > covering > LLVM, we have begun a series dedicated to the design and > implementation of >

On Thursday 18 June 2009 12:28:57 Cory Nelson wrote: > I'm also curious what language uses this and why it is useful :) HLVM is intended to be a general-purpose VM rather than a particular language. > Also, things like this would make lock-free algorithms difficult or > impossible. True. Perhaps that is a good argument for providing both kinds. However, nulls are certainly more

> > That is similar to the approach I used, although HLVM provides a pointer directly to the type, saving you a single hop. I'm not so sure that is a very good reason, depending on your implementation data structures that are fundamental to the type system of the virtual machine use custom allocators so the extra hop carries little to no expense. I would not have considered it had I

The (new) HLVM project is continuing to improve and I have graphed and analysed some performance-related data. Beating OCaml on numerical performance using LLVM turned out to be quite easy on x86: http://flyingfrogblog.blogspot.com/2009/03/performance-ocaml-vs-hlvm-beta-04.html This was achieved using a single optimization pass in HLVM (unrolling) and none of LLVM's own IR optimization

Hi, I am senior student at Tashkent University of Information Technologies and I am highly interested in programming language design. I want to develop Python front-end for HLVM as a part of LLVM participation in Google Summer of Code project. I am in long love with Python programming language for its simplicity and effectiveness. Last year I noticed ShedSkin Python to C++ translator among SoC

The HLVM project is a high-level VM optimized for scientific computing: http://www.ffconsultancy.com/ocaml/hlvm/ I implemented the first-working version of a garbage collector capable of collecting from threads that run in parallel in November. Initial performance was awful due to the overhead of accessing thread-local data via POSIX pthreads. I just completed optimizing HLVM so

What happened to the HLVM project? I understand it was intended to be a high-level VM specifically for dynamic languages and this post indicates that it was integrated into the LLVM project last year: http://www.nabble.com/NEWS:-HLVM-merges-with-LLVM-td9627113.html But I cannot find any code in LLVM that looks like it would have come from HLVM. -- Dr Jon Harrop, Flying Frog Consultancy

On Sun, Jan 4, 2009 at 2:36 PM, Jon Harrop <jon at ffconsultancy.com> wrote: (...) > But I cannot find any code in LLVM that looks like it would have come from > HLVM. Don't know about the status of the project, but the code seems to be here: http://llvm.org/viewvc/llvm-project/ (in directory "hlvm") Regards, Kevin André

The ocamldoc-generated documentation for HLVM is now available here: http://www.ffconsultancy.com/ocaml/hlvm/docs/ -- Dr Jon Harrop, Flying Frog Consultancy Ltd. http://www.ffconsultancy.com/?e

Gabe, I'm quite new to hacking on LLVM, but I'll give you an idea I had reading some of the recent dev list posts. I think investigating concurrency with regards to LLVM would be very useful (what with multi-cores and all). This could be concurrency in regards to GC, or it could be simply looking at how LLVM can best interface with standard concurrency paradigms (OpenMP, MPI)

Hello, I would also like to apply for Google's Summer of Code, but I am having difficulty finding a concrete project idea to tackle. (Though certainly interesting, a new front-end or a compiler optimization pass seem like to large as projects for a single summer -- and certainly something I couldn't accomplish given my lack of familiarity with the code-base.) I have read the

To illustrate the value of value types to the OCaml community I recently did a couple of benchmarks. The first was similar to a hash table and stores key-value pairs unboxed in an array: http://groups.google.com/group/fa.caml/msg/8430ebdb687b9268 The second is the hailstone benchmark that the Haskell guys found gave huge performance improvements when using LLVM from GHC:

Jon Harrop wrote: > The simplest way is surely to reuse HLVM because it provides everything you > need and is even written in the right language! ;-) Is there a web page with HLVM docs? There's a README.txt in the subversion repository: https://llvm.org/svn/llvm-project/hlvm/trunk/README.txt which says: HLVM comes with documentation in HTML format. These are provided in

The LLVM 2.6-compatible IR below is derived from the HLVM test suite and is one of the things I've noticed going wrong. However, I just discovered that it works with LLVM 2.6 and with LLVM SVN when run through lli or llc without -tailcallopt but when I use: $ llvm-as -f aout.ll $ llc -tailcallopt -f aout.bc -o aout.s $ gcc -lm aout.s -o aout and the latest LLVM SVN it starts to print

Would you then agree with me that "LLVM's garbage collection facilities, _as described in the LLVM documentation_, are too difficult to use"? On Tue, Dec 6, 2011 at 3:40 AM, Jon Harrop < jonathandeanharrop at googlemail.com> wrote: > Talin wrote: > > Jon wrote: > > > Talin wrote: > > > > Garbage collection is still way too difficult. > >

Talin wrote: > Jon wrote: > > Talin wrote: > > > Garbage collection is still way too difficult. > > > > This is completely untrue. > > I'm afraid I'm going to have to disagree... I failed to get my point across. You're still talking about the difficulty of using LLVM's GC support. I was talking about circumventing it. The shadow stack HLVM uses