linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: sparse-llvm results from trying to compile a largish program
Date: Tue, 14 Mar 2017 13:17:31 +0000	[thread overview]
Message-ID: <CACXZuxf02DM+spQckV0CyycaY7dqUbuM9wuKNktaRMndvtfpBQ@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxdT9fXHnysUFUoMqe+dEuDSKHsQS3Tn8KFEfAP2cnAnJA@mail.gmail.com>

On 13 March 2017 at 19:34, Dibyendu Majumdar <mobile@majumdar.org.uk> wrote:
> I tried to compile a Lua implementation using sparse-llvm. This
> particular implementation is called 'minilua' as it is a cut down
> version of Lua 5.1.5 created by Mike Pall for the LuaJIT project.
>
> I had to change all static initializations of course as these are
> unsupported in sparse-llvm. I also had to add support for casting
> floating point values to integer type in 'op_cast' implementation.
>
> sparse-llvm managed to consume the program after these changes but
> there were many LLVM errors reported, which indicates that the
> generated code is incorrect.
>
> I have saved the results from this exercise here:
>
> https://github.com/dibyendumajumdar/dmr_c/tree/master/tests/minilua
>
> Hopefully this will help in analysing the errors and deciding how to fix them.
>

I have fixed a bunch of issues in my repository - and the updated
error list now is much reduced! Please see the link above for the
remaining errors and the generated code.

Thanks and Regards
Dibyendu

  reply	other threads:[~2017-03-14 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-13 19:34 sparse-llvm results from trying to compile a largish program Dibyendu Majumdar
2017-03-14 13:17 ` Dibyendu Majumdar [this message]
2017-03-14 15:56   ` Dibyendu Majumdar

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=CACXZuxf02DM+spQckV0CyycaY7dqUbuM9wuKNktaRMndvtfpBQ@mail.gmail.com \
    --to=mobile@majumdar.org.uk \
    --cc=linux-sparse@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).