From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [GIT PULL] llvm fixes
Date: Sun, 12 Nov 2017 06:45:52 +0100 [thread overview]
Message-ID: <20171112054550.cppako2mchvyhmmg@ltop.local> (raw)
In-Reply-To: <CANeU7Q=qa4Je13z65nHa_V=QAC4w-30GiO3e72Lp5C49QYcDVg@mail.gmail.com>
On Sun, Nov 12, 2017 at 09:04:43AM +0800, Christopher Li wrote:
> - create special instruction that is not part of bb->insns. Push
> instruction in insn.arguments.
You already came with this previously and I already replied you about it.
I don't know what make you think that OP_PUSH are not in bb->insns
but you're wrong: they are normal instructions and are thus stored
in the bb->insns, the second patch even change their position inside
this list.
-- Luc
next prev parent reply other threads:[~2017-11-12 5:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 9:51 [GIT PULL] llvm fixes Luc Van Oostenryck
2017-10-02 19:49 ` Luc Van Oostenryck
2017-10-16 14:41 ` Luc Van Oostenryck
2017-10-29 23:13 ` Christopher Li
2017-11-05 8:29 ` Christopher Li
2017-11-05 17:10 ` Luc Van Oostenryck
2017-11-05 23:18 ` Christopher Li
2017-11-12 1:04 ` Christopher Li
2017-11-12 5:05 ` Luc Van Oostenryck
2017-11-12 10:10 ` Christopher Li
2017-11-12 5:45 ` Luc Van Oostenryck [this message]
2017-11-05 8:49 ` Christopher Li
2017-11-05 17:03 ` Luc Van Oostenryck
2017-10-29 23:31 ` Christopher Li
2017-10-30 6:14 ` Luc Van Oostenryck
2017-11-17 9:51 ` Luc Van Oostenryck
[not found] ` <CANeU7QnTtcKP9ukNqGmMzfVMviYwYEfYFhgLRHHGxCqR7sPGEQ@mail.gmail.com>
2017-11-17 19:50 ` Luc Van Oostenryck
2017-11-26 17:42 ` Christopher Li
2017-11-26 19:34 ` 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=20171112054550.cppako2mchvyhmmg@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.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 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.