linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Xi Wang <xi.wang@gmail.com>
Cc: Pekka Enberg <penberg@kernel.org>,
	linux-sparse@vger.kernel.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Christopher Li <sparse@chrisli.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC][PATCH 0/3] implement pseudo->ctype
Date: Sat, 09 Jun 2012 08:06:46 -0400	[thread overview]
Message-ID: <4FD33C56.1080207@garzik.org> (raw)
In-Reply-To: <2055A8E4-5846-4913-9E57-5BBDCB868284@gmail.com>

On 06/09/2012 07:52 AM, Xi Wang wrote:
> Besides, the phi nodes in sparse and LLVM are different.  LLVM's
> phi 1) requires one entry for each predecessor, and 2) must stay
> at the beginning of a block.  I didn't find an easy way to translate
> sparse's phi to LLVM's, so instead generated load/store for phi
> nodes.

That is reasonable.

	Jeff


  reply	other threads:[~2012-06-09 12:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04  6:54 [RFC][PATCH 0/3] implement pseudo->ctype Xi Wang
2012-06-04  6:54 ` [RFC][PATCH 1/3] add ->ctype to struct pseudo Xi Wang
2012-06-04  6:54 ` [RFC][PATCH 2/3] remove ->type and ->size from struct instruction Xi Wang
2012-06-04  6:54 ` [RFC][PATCH 3/3] sparse, llvm: sync with new " Xi Wang
2012-06-08 11:50 ` [RFC][PATCH 0/3] implement pseudo->ctype Pekka Enberg
2012-06-08 15:39   ` Xi Wang
2012-06-09  1:35 ` Xi Wang
2012-06-09 10:42   ` Pekka Enberg
2012-06-09 11:52     ` Xi Wang
2012-06-09 12:06       ` Jeff Garzik [this message]
2012-06-09 12:12       ` Pekka Enberg
2012-06-21 10:00 ` Christopher Li
2012-06-22  2:08   ` Xi Wang
2012-06-22 17:59     ` 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=4FD33C56.1080207@garzik.org \
    --to=jeff@garzik.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=penberg@kernel.org \
    --cc=sparse@chrisli.org \
    --cc=torvalds@linux-foundation.org \
    --cc=xi.wang@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).