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: Tue, 28 Feb 2017 18:08:16 +0000 [thread overview]
Message-ID: <CACXZuxdFQD+6yPcisZ=hJssO5fyxm9LYJbvVHsvnjRz87cCjrQ@mail.gmail.com> (raw)
In-Reply-To: <20170228173519.hyq3aihtg3zouoih@macpro.local>
On 28 February 2017 at 17:35, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
> Not very pretty and incomplete but the following patch allow sparse-llvm
> to compile this:
> struct mytype {
> int *foo;
> };
>
> extern void init_mytype(struct mytype *mt);
> void init_mytype(struct mytype *mt)
> {
> mt->foo = (int *)mt;
> mt->foo = (void *)mt;
> mt->foo = (int *)0;
> mt->foo = (void *)0;
> mt->foo = (void *)(long)0;
> }
>
> It fail at " ... = (... *)1;" though.
>
>
> + type = insn_symbol_type(fn->module, insn);
> + switch (LLVMGetTypeKind(type)) {
> + case LLVMPointerTypeKind:
> + assert(!pseudo->value);
> + result = LLVMConstPointerNull(type);
> + break;
> + case LLVMIntegerTypeKind:
> + result = LLVMConstInt(type, pseudo->value, 1);
> + break;
> + default:
> + assert(0);
> + }
Following modified version should handle values than 0.
LLVMTypeRef type = insn_symbol_type(fn->module, insn);
switch (LLVMGetTypeKind(type)) {
case LLVMPointerTypeKind:
if (pseudo->value == 0)
result = LLVMConstPointerNull(type);
else
result = LLVMConstIntToPtr(LLVMConstInt(LLVMIntType(bits_in_pointer),
pseudo->value, 1), type);
break;
case LLVMIntegerTypeKind:
result = LLVMConstInt(type, pseudo->value, 1);
break;
default:
assert(0);
}
Regards
Dibyendu
next prev parent reply other threads:[~2017-02-28 18:08 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 [this message]
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
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='CACXZuxdFQD+6yPcisZ=hJssO5fyxm9LYJbvVHsvnjRz87cCjrQ@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 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).