From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Sparse-LLVM issue compiling NULL pointers
Date: Thu, 2 Mar 2017 07:48:30 +0100 [thread overview]
Message-ID: <CAExDi1TRL+zXQ_C5iDiVuWkUdmk8A=-sd1PRAzeZY7QdWirKNg@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxeq=ZOTroVmtHqjNpPzFw-nvu4beWfXeVUhBnaBt12gjA@mail.gmail.com>
On Tue, Feb 28, 2017 at 5:49 PM, Dibyendu Majumdar
<mobile@majumdar.org.uk> wrote:
>
> I should add that if (int *) is used instead of (void *) in the above
> example, it still aborts, although this time the changes I suggested
> are not relevant.
Strange. It seems to work correctly for me.
Luc
next prev parent reply other threads:[~2017-03-02 6:48 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 [this message]
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
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='CAExDi1TRL+zXQ_C5iDiVuWkUdmk8A=-sd1PRAzeZY7QdWirKNg@mail.gmail.com' \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=mobile@majumdar.org.uk \
/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.