From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Sparse-LLVM issue compiling NULL pointers
Date: Thu, 2 Mar 2017 18:02:10 +0000 [thread overview]
Message-ID: <CACXZuxfR6HNzvzkCLy1R2bik4R2p9t1i1+fga91GP-SnMAkwmQ@mail.gmail.com> (raw)
In-Reply-To: <CAExDi1QY1+KEsdzBuy0aorDwzvoL2Vos-F5P1HsJZCjT9o0R0w@mail.gmail.com>
On 2 March 2017 at 17:57, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
>> Removing the last line of output_op_store() (insn->target->priv = target;)
>> should fix this.
>
> In fact LLVMBuildStore() return a LLVMValueRef.
> Could this be the 'void' we seen?
>
It returns a Value that is a store instruction, or at least that's the
way I interpret this and so yes, I think the type of this was void.
BTW removing the line makes progress, but it fails at the add
instruction later. Are there other issues like this you can spot? I am
a bit lost here I am afraid.
Regards
next prev parent reply other threads:[~2017-03-03 2:21 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 6:20 Sparse-LLVM issue compiling NULL pointers Dibyendu Majumdar
2017-02-28 15:09 ` Luc Van Oostenryck
2017-02-28 16:04 ` Dibyendu Majumdar
2017-02-28 16:47 ` Luc Van Oostenryck
2017-02-28 16:49 ` Dibyendu Majumdar
2017-03-02 6:48 ` Luc Van Oostenryck
2017-02-28 17:03 ` Luc Van Oostenryck
2017-02-28 17:35 ` Luc Van Oostenryck
2017-02-28 17:42 ` Dibyendu Majumdar
2017-02-28 18:08 ` Dibyendu Majumdar
2017-03-01 5:49 ` Luc Van Oostenryck
2017-03-02 7:02 ` [PATCH] llvm: fix getting type of values Luc Van Oostenryck
2017-03-01 10:58 ` Sparse-LLVM issue compiling NULL pointers Dibyendu Majumdar
2017-03-01 14:45 ` Dibyendu Majumdar
2017-03-02 5:21 ` Luc Van Oostenryck
2017-03-02 5:41 ` Dibyendu Majumdar
2017-03-02 13:56 ` Luc Van Oostenryck
2017-03-02 14:05 ` Dibyendu Majumdar
2017-03-02 16:10 ` Luc Van Oostenryck
2017-03-02 14:33 ` Dibyendu Majumdar
2017-03-02 16:04 ` Luc Van Oostenryck
2017-03-02 16:29 ` Dibyendu Majumdar
2017-03-02 16:30 ` Dibyendu Majumdar
2017-03-02 17:18 ` Luc Van Oostenryck
2017-03-02 17:36 ` Dibyendu Majumdar
2017-03-02 20:09 ` Luc Van Oostenryck
2017-03-03 2:52 ` Dibyendu Majumdar
2017-03-03 3:01 ` Dibyendu Majumdar
2017-03-03 4:03 ` Dibyendu Majumdar
2017-03-03 5:24 ` [PATCH] llvm: fix output_op_[ptr]cast() Luc Van Oostenryck
2017-03-03 7:37 ` Dibyendu Majumdar
2017-03-03 18:06 ` Dibyendu Majumdar
2017-03-03 18:30 ` Dibyendu Majumdar
2017-03-03 19:55 ` Luc Van Oostenryck
2017-03-06 1:56 ` Christopher Li
2017-03-03 19:50 ` Luc Van Oostenryck
2017-03-03 19:54 ` Dibyendu Majumdar
2017-03-03 20:52 ` [PATCH] llvm: fix: do not mix pointers and floats when doing compares Luc Van Oostenryck
2017-03-03 4:16 ` Sparse-LLVM issue compiling NULL pointers Luc Van Oostenryck
2017-03-03 4:27 ` Luc Van Oostenryck
2017-03-03 4:38 ` Dibyendu Majumdar
2017-03-03 7:50 ` Luc Van Oostenryck
2017-03-03 12:39 ` Dibyendu Majumdar
2017-03-02 17:03 ` Dibyendu Majumdar
2017-03-02 17:18 ` Dibyendu Majumdar
2017-03-02 17:43 ` Luc Van Oostenryck
2017-03-02 18:58 ` Dibyendu Majumdar
2017-03-02 19:34 ` Luc Van Oostenryck
2017-03-02 17:50 ` Luc Van Oostenryck
2017-03-02 17:57 ` Luc Van Oostenryck
2017-03-02 18:02 ` Dibyendu Majumdar [this message]
2017-03-03 4:21 ` Luc Van Oostenryck
2017-03-02 17:27 ` Luc Van Oostenryck
2017-03-02 18:41 ` Dibyendu Majumdar
2017-03-03 5:35 ` Luc Van Oostenryck
2017-03-02 16:39 ` Dibyendu Majumdar
2017-03-02 17:21 ` Luc Van Oostenryck
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=CACXZuxfR6HNzvzkCLy1R2bik4R2p9t1i1+fga91GP-SnMAkwmQ@mail.gmail.com \
--to=mobile@majumdar.org.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.