From: Christopher Li <sparse@chrisli.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Dibyendu Majumdar <mobile@majumdar.org.uk>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: [PATCH 0/2] V2 llvm constant value pseudo size fix
Date: Mon, 13 Nov 2017 23:27:54 +0800 [thread overview]
Message-ID: <CANeU7QknH=xpuButjBpVved131s8Kw4AJRZZGTBDLN+LBH_H9A@mail.gmail.com> (raw)
Per Luc's feed back. This is the more complete version
of the pseudo-size-value branch.
I add the second patch to allow sparse-llvm to use
the new size store in constant value pseudo.
The whole series is very simple, only two patches.
It directly address the problem of sparse-llvm wasn't
able to get the integer size from constant value pseudo.
I am consider this as better alternative compare to OP_PUSH.
- OP_PUSH break byte code compatibility at source level, this does not.
- OP_PUSH has more instruction (more memory).
- OP_PUSH only cover constant value used in function call.
this cover all usage of constant value.
It pass the "make check" test ( I have to fix a problem with
the bool type which is 1 bit integer). The V1 pass the kernel
checker test with no change to output.
Dibyendu, can you give this series some test since you report
it?
The git url:
https://git.kernel.org/pub/scm/devel/sparse/chrisl/sparse.git/log/?h=pseudo-sized-value-v2
Chris
next reply other threads:[~2017-11-13 15:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 15:27 Christopher Li [this message]
2017-11-13 20:31 ` [PATCH 0/2] V2 llvm constant value pseudo size fix Dibyendu Majumdar
2017-11-13 23:23 ` 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='CANeU7QknH=xpuButjBpVved131s8Kw4AJRZZGTBDLN+LBH_H9A@mail.gmail.com' \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--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 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).