From: "Ulrich Schöpp" <schoepp@tcs.ifi.lmu.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] LLVM debug information
Date: Fri, 22 Apr 2016 10:46:44 +0200 [thread overview]
Message-ID: <5719E4F4.1070203@tcs.ifi.lmu.de> (raw)
In-Reply-To: <trinity-af5764e3-64a3-47b6-8c7a-411e73e130e5-1461272826958@3capp-webde-bs06>
[-- Attachment #1.1: Type: text/plain, Size: 1309 bytes --]
Hi,
have you seen that the go bindings already contain a C wrapper for the
DIBuilder class?
https://github.com/llvm-mirror/llvm/blob/master/bindings/go/llvm/DIBuilderBindings.h
It contains this comment:
// FIXME: These bindings shouldn't be Go-specific and should eventually
// move to a (somewhat) less stable collection of C APIs for use in
// creating bindings of LLVM in other languages.
I would also be interested in OCaml bindings for this.
Best,
Ulrich
On 21/04/16 23:07, picflo_2@web.de wrote:
> Hi all,
>
> at the company I currently work for LLVM is used for the backend of a
> DSL. Since this DSL is missing a debugger
> i was looking into this topic and what would actually be missing to add
> the required information to use something like
> lldb or gdb or even link it to the Visual Studio MI Debug Engine to
> debug the resulting code. If I understand it correctly
> the OCaml LLVM bindings only give access to the IRBuilder class and not
> the required DIBuilder class? Would it be sufficient
> to add at first the C wrapper for the DIBuilder class and then the OCaml
> bindings using these C wrapper to add debug information
> to the offical LLVM repo to start writing a DSL specific debugger using
> OCaml?
>
> Best regards,
>
> Florian
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-04-22 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 21:07 picflo_2
2016-04-22 8:46 ` Ulrich Schöpp [this message]
2016-04-22 9:51 ` Aw: " picflo_2
2016-05-02 16:15 ` whitequark
2016-05-04 13:18 ` Aw: " picflo_2
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5719E4F4.1070203@tcs.ifi.lmu.de \
--to=schoepp@tcs.ifi.lmu.de \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox