From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
Christopher Li <sparse@chrisli.org>,
Pekka Enberg <penberg@kernel.org>, Jeff Garzik <jeff@garzik.org>
Subject: Re: [PATCH v2 00/27] LLVM fixes
Date: Sat, 11 Mar 2017 11:12:20 +0000 [thread overview]
Message-ID: <CACXZuxc8rbcGSO9dTkFSKST8UJkDgc2ifFae5=Y+cojtm5qb3Q@mail.gmail.com> (raw)
In-Reply-To: <20170311090706.17171-1-luc.vanoostenryck@gmail.com>
Hi Luc,
On 11 March 2017 at 09:06, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
> This series solves a number of issues in sparse-llvm,
> mainly about wrong or missing type information as needed
> to build LLVM IR.
> These issues have been reported and investigated by
> Dibyendu Majumdar.
>
> * patches 1-4 adds missing type info in sparse's IR
> * patch 4 is not needed by this serie but logically belong
> to the same group as patches 1-3. It can be dropped.
> * patches 5-7 are fixes
> * patch 8 makes debugging easier
> * patches 8-10 are preparatory steps for patch 11
> * patches 11 & 12 are fixes
> * patch 13 is a preparatory step for patch 14
> * patch 14 solves a lot of issues
> * patches 15-18 are test cases solved by patch 14
> * patch 19 & 20 are fixes
> * patches 21, 23-27 are cleanups
> * patch 22 makes debugging easier
>
>
Thank you very much for this series of patches. I have merged them
into my project and things are better. We still cannot invoke
functions via pointers to functions using the (*ident)(arg) syntax due
to the incorrect load operation output by the linearizer.
I have been trying to compile a smallish program (AVL Tree
implementation) - making progress but it still fails to compile, so I
will report the next issue!
Thanks and Regards
Dibyendu
next prev parent reply other threads:[~2017-03-11 11:12 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 9:06 [PATCH v2 00/27] LLVM fixes Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 01/27] give a type to OP_PHISOURCE Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 02/27] give a type to OP_SEL, always Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 03/27] give a type to OP_SYMADDR Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 04/27] give a type to PSEUDO_ARGs Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 05/27] llvm: fix translation of PSEUDO_VALs into a ValueRefs Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 06/27] llvm: fix output_op_store() which modify its operand Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 07/27] llvm: fix output_op_[ptr]cast() Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 08/27] llvm: give a name to call return values Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 09/27] llvm: add test cases for the type of constants Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 10/27] add ptr_list_nth_entry() Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 11/27] llvm: fix type of literal integer passed as arguments Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 12/27] llvm: fix output OP_ADD mixed with pointers Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 13/27] llvm: add support for OP_SYMADDR Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 14/27] keep OP_SYMADDR instructions Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 15/27] llvm: add test cases for symbol's address Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 16/27] llvm: add test cases for pointers passed as argument Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 17/27] llvm: add test cases for arrays " Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 18/27] llvm: add test cases for degenerated pointers Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 19/27] llvm: add support for OP_NEG Luc Van Oostenryck
2017-03-11 9:06 ` [PATCH v2 20/27] llvm: fix pointer/float mixup in comparisons Luc Van Oostenryck
2017-03-11 9:07 ` [PATCH v2 21/27] llvm: use pseudo_list_size() instead of open coding it Luc Van Oostenryck
2017-03-11 9:07 ` [PATCH v2 22/27] llvm: give arguments a name Luc Van Oostenryck
2017-03-11 9:07 ` [PATCH v2 23/27] llvm: remove unneeded arg 'module' Luc Van Oostenryck
2017-03-11 9:07 ` [PATCH v2 24/27] llvm: remove unneeded arg 'fn' Luc Van Oostenryck
2017-03-11 9:07 ` [PATCH v2 25/27] llvm: remove unneeded 'generation' Luc Van Oostenryck
2017-03-11 9:07 ` [PATCH v2 26/27] llvm: remove unneeded function::type Luc Van Oostenryck
2017-03-11 9:07 ` [PATCH v2 27/27] llvm: reduce scope of 'bb_nr' Luc Van Oostenryck
2017-03-11 11:12 ` Dibyendu Majumdar [this message]
2017-03-11 11:49 ` [PATCH v2 00/27] LLVM fixes Luc Van Oostenryck
2017-03-11 11:54 ` Dibyendu Majumdar
2017-03-11 12:30 ` Luc Van Oostenryck
2017-03-11 13:36 ` Dibyendu Majumdar
2017-03-11 14:12 ` Luc Van Oostenryck
2017-03-11 14:16 ` Dibyendu Majumdar
2017-03-11 14:28 ` Luc Van Oostenryck
2017-03-11 15:10 ` Jeff Garzik
2017-03-11 15:51 ` Luc Van Oostenryck
2017-03-11 18:08 ` Dibyendu Majumdar
2017-03-11 20:44 ` Luc Van Oostenryck
2017-03-11 21:21 ` Dibyendu Majumdar
2017-03-11 22:30 ` Luc Van Oostenryck
2017-03-11 22:57 ` Dibyendu Majumdar
2017-03-11 23:02 ` Linus Torvalds
2017-03-11 23:04 ` Dibyendu Majumdar
2017-03-11 23:12 ` Luc Van Oostenryck
2017-03-12 2:35 ` Dibyendu Majumdar
2017-03-14 6:18 ` Christopher Li
2017-03-16 16:41 ` Luc Van Oostenryck
2017-03-17 14:06 ` Dibyendu Majumdar
2017-03-17 17:04 ` Christopher Li
2017-03-17 17:41 ` Luc Van Oostenryck
2017-03-17 18:05 ` Christopher Li
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='CACXZuxc8rbcGSO9dTkFSKST8UJkDgc2ifFae5=Y+cojtm5qb3Q@mail.gmail.com' \
--to=mobile@majumdar.org.uk \
--cc=jeff@garzik.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=penberg@kernel.org \
--cc=sparse@chrisli.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).