From: Xi Wang <xi.wang@gmail.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Jeff Garzik" <jgarzik@pobox.com>,
linux-sparse@vger.kernel.org,
"Christopher Li" <sparse@chrisli.org>,
"Jeff Garzik" <jgarzik@redhat.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>
Subject: Re: [PATCH 1/2] sparse, llvm: group PHI nodes at the top of each BB
Date: Wed, 17 Oct 2012 02:53:48 -0400 [thread overview]
Message-ID: <507E55FC.5010202@gmail.com> (raw)
In-Reply-To: <CAOJsxLFXaWXcR8vF_DFPAaJZPJ_BTe47Q9GSkM-2MChaRBqkdw@mail.gmail.com>
On 10/17/12 2:48 AM, Pekka Enberg wrote:
> Is LLVM able to optimize away the allocas and use registers instead in
> the emitted code?
Yes. See the last part of my previous email, no load/store/alloca after
LLVM's -mem2reg pass.
- xi
next prev parent reply other threads:[~2012-10-17 6:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 23:34 [PATCH 1/2] sparse, llvm: group PHI nodes at the top of each BB Jonathan Neuschäfer
2012-10-09 23:34 ` [PATCH 2/2] sparse, llvm: Fix type of loaded values Jonathan Neuschäfer
2012-10-10 0:13 ` Jeff Garzik
2012-10-10 6:34 ` Pekka Enberg
2012-10-10 0:12 ` [PATCH 1/2] sparse, llvm: group PHI nodes at the top of each BB Jeff Garzik
2012-10-10 6:31 ` Pekka Enberg
2012-10-10 16:33 ` Jonathan Neuschäfer
2012-10-12 18:25 ` Pekka Enberg
2012-10-16 17:59 ` Pekka Enberg
2012-10-16 20:14 ` Jonathan Neuschäfer
2012-10-16 20:53 ` Xi Wang
2012-10-17 6:48 ` Pekka Enberg
2012-10-17 6:53 ` Xi Wang [this message]
2012-10-17 16:41 ` Pekka Enberg
2012-10-17 17:44 ` Jonathan Neuschäfer
2013-05-15 12:05 ` Pekka Enberg
2013-05-16 5:28 ` Xi Wang
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=507E55FC.5010202@gmail.com \
--to=xi.wang@gmail.com \
--cc=j.neuschaefer@gmx.net \
--cc=jgarzik@pobox.com \
--cc=jgarzik@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=sparse@chrisli.org \
--cc=torvalds@linux-foundation.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.