search for: ocamlyacc

...n for using LLVM in my own project. While the tutorial is very helpful, it was somewhat hard to start due to the fact that I plan on using ocamllex and ocmalyacc and the tutorial hand rolls their own lexer and parser. I have managed to adapt almost all of the tutorial code into using ocamllex and ocamlyacc (the only thing I'm missing is the ability to assign precendence to user defined binary and unary operators), and was wondering if ther would be an interest in adding my code as supplimental material. Sincerely, Chris Wailes -------------- next part -------------- An HTML attachment was scrubb...

...wn project.  While the tutorial is very helpful, it > was somewhat hard to start due to the fact that I plan on using ocamllex and > ocmalyacc and the tutorial hand rolls their own lexer and parser. > > I have managed to adapt almost all of the tutorial code into using ocamllex > and ocamlyacc (the only thing I'm missing is the ability to assign > precendence to user defined binary and unary operators), and was wondering > if ther would be an interest in adding my code as supplimental material. Great! I'd be happy to add this, though I think as as an addendum instead of a...

...ied it the pre-processor executable had not been created and installed. When the compiler tried to pass it through, it couldn't find anything. It has been a little bit since I tried, and there may have been updates, so the issue may have been fixed. Well you still run into that with ocamllex/ocamlyacc :) Maybe I'm just > used to the stream syntax extension, but I figured it was fair game > since it's part of the standard install. It's not my fault the fedora > project decided to make it not part of the standard ocaml install :) That is perfectly understandable. My problem...

...g and other kinds of VSA> checking. OK, concerning AST -- I see. Thank you. VSA> For OCAML, for example, the front-end is quite sophisticated VSA> and complex and the LLVM representation would not be suitable for VSA> supporting all the checking and translation. But I have just meant ocamlyacc, i.e. ocaml clone of the yacc. And here my question was: what kind of interface is expected to use from within ocml, CommonLisp implementations, Haskel and other nice language implementations? What is the expected way of interfacing LLVM for those non-C language implementations? shared libraries wi...

...er is "of course we need an internal semantic tree between parsing and LLVM!" But I am still wondering what are your strategic plans conserning this issue. 2. For other (not C/C++) languages there should be some interface solution in order to use LLVM from their parsers (e.g. ocamlyacc). So, what about that? Thank you. -- Best regards, Valery mailto:khamenya at mail dot ru

Attached are alternative the files for chapters 1-7 that use ocamlyacc and ocamllex. I have cleaned them up and debugged them as best I can but I may have missed something, so any comments on them would be great. Also, the LLVM-OCaml bindings are messed up in Fedora 10 (some of the binary files point to their origonal build directory) so I had to put in a dirty hack...

On Tuesday 14 April 2009 01:29:44 Chris Wailes wrote: > I have managed to adapt almost all of the tutorial code into using ocamllex > and ocamlyacc (the only thing I'm missing is the ability to assign > precendence to user defined binary and unary operators), and was wondering > if ther would be an interest in adding my code as supplimental material. Yes! I thought it was a bit of a shame that so much precious LLVM tutorial space w...

> VSA> For OCAML, for example, the front-end is quite sophisticated > VSA> and complex and the LLVM representation would not be suitable for > VSA> supporting all the checking and translation. > > But I have just meant ocamlyacc, i.e. ocaml clone of the yacc. > And here my question was: what kind of interface is expected to use > from within ocml, CommonLisp implementations, Haskel and other nice > language implementations? What is the expected way of interfacing > LLVM for those non-C language implementations?...

...> an internal semantic tree between parsing and LLVM!" > But I am still wondering what are your strategic plans conserning > this issue. > > 2. For other (not C/C++) languages there should be some interface > solution in order to use LLVM from their parsers (e.g. ocamlyacc). > So, what about that? > > Thank you. > > -- > Best regards, > Valery mailto:khamenya at mail dot ru > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs....

...x/yacc. You may also be interested in this LLVM-based example in OCaml that uses camlp4 for parsing directly: http://groups.google.com/group/fa.caml/msg/5aee553df34548e2 > Secondly, it seems odd to be writing custom parsers > and lexers after tools like Bison and Flex (and ocamllex and ocamlyacc) > have been around for some time. Is there any particular reason the C++ > tutorial is using hand coded parsers and lexers? Is there a technical > reason? I found flex and bison really tedious to use from C++. That was a long time ago and there are probably better alternatives now th...

...bs/log libs/xc libs/eventchn \ - libs/xb libs/xs + libs/xb libs/xs libs/xl SUBDIRS_PROGRAMS = xenstored diff --git a/tools/ocaml/common.make b/tools/ocaml/common.make index 63b6b2e..a2085d7 100644 --- a/tools/ocaml/common.make +++ b/tools/ocaml/common.make @@ -9,7 +9,7 @@ OCAMLLEX ?= ocamllex OCAMLYACC ?= ocamlyacc CFLAGS += -fPIC -Werror -CFLAGS += -I$(TOPLEVEL)/../include -I$(TOPLEVEL)/../libxc +CFLAGS += -I$(TOPLEVEL)/../include -I$(TOPLEVEL)/../libxc -I$(TOPLEVEL)/../xenstore -I$(TOPLEVEL)/../libxl CFLAGS-$(CONFIG_Linux) += -I/usr/lib64/ocaml -I/usr/lib/ocaml CFLAGS-$(CONFIG_NetBSD) += -...

This is something I've been working on: Reworking inspection so it's not a big mess of ad hoc C code, but instead uses a well-defined domain-specific language to describe how we inspect guests. The best introduction to this is the manual page, which I include below (it's also included in patch 2/3). Rich. ---------------------------------------------------------------------- NAME

Previously posted: https://www.redhat.com/archives/libguestfs/2015-December/msg00038.html Inspection now really succeeds on a small number of simple guests. To test it out: $ ./run guestfish -v -x -a /tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection --verbose" Rich.

This is a more working version. Inspection (partially) succeeds on a real guest this time :-) You can test it out on a real guest (in this case, a CentOS disk image located at /tmp/centos-6.img) by doing: $ ./run guestfish -v -x -a /tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection --verbose" which will print lots of debugging, and at the end the

For background on this change, see: https://rwmj.wordpress.com/2015/12/06/inspection-now-with-added-prolog/ v2 was previously posted here: https://www.redhat.com/archives/libguestfs/2015-December/msg00038.html To test this patch series on a real guest, you can do: $ ./run guestfish -v -x -a /var/tmp/centos-6.img ><fs> run ><fs> debug sh "guestfs-inspection