From: Jeff Garzik <jeff@garzik.org>
To: Pekka Enberg <penberg@kernel.org>
Cc: Xi Wang <xi.wang@gmail.com>,
linux-sparse@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Christopher Li <sparse@chrisli.org>,
Jeff Garzik <jgarzik@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC/PATCH] sparse, llvm: Fix string globals access
Date: Sat, 09 Jun 2012 08:08:26 -0400 [thread overview]
Message-ID: <4FD33CBA.4010903@garzik.org> (raw)
In-Reply-To: <CAOJsxLFX-ZiDCQ84uKka4MYa_uUhLMPeR=XWAHMevTRFsfZBJA@mail.gmail.com>
On 06/09/2012 07:00 AM, Pekka Enberg wrote:
> Jeff, I guess we should do this for output_load() and output_store()
> in sparse-llvm.c as well?
Yes, that is a definite improvement over the current hackery in
output_op_load()
prev parent reply other threads:[~2012-06-09 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 12:58 [RFC/PATCH] sparse, llvm: Fix string globals access Pekka Enberg
2012-06-08 18:13 ` Jeff Garzik
2012-06-08 20:39 ` Pekka Enberg
2012-06-08 23:55 ` Xi Wang
2012-06-09 11:00 ` Pekka Enberg
2012-06-09 11:46 ` Xi Wang
2012-06-09 12:08 ` Jeff Garzik [this message]
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=4FD33CBA.4010903@garzik.org \
--to=jeff@garzik.org \
--cc=benh@kernel.crashing.org \
--cc=jgarzik@redhat.com \
--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).