linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@kernel.org>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org, Jeff Garzik <jgarzik@redhat.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Xi Wang <xi.wang@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: [GIT PULL] LLVM backend updates
Date: Sat, 9 Jun 2012 14:11:04 +0300 (EEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1206091408320.4769@tux.localdomain> (raw)

Hi Chris,

Please pull the latest sparse-llvm tree from:

  git@github.com:penberg/sparse-llvm.git for-chris

It has one new validation test case and fixes to handle strings properly 
in the LLVM backend.

			Pekka
------------------>

The following changes since commit 970d7169d75068146152ba01a66381c800dbeb71:

  I have updated the sparse.1 man page including the __bitwise relevant 
content, and created Documentation/sparse.txt with the complete comparison 
between __nocast vs __bitwise. (2012-05-19 23:42:36 -0700)

are available in the git repository at:
  git@github.com:penberg/sparse-llvm.git for-chris

Pekka Enberg (4):
      sparse, llvm: Add _Bool to cast validation test
      sparse, llvm: Simplify output_data() type logic
      sparse, llvm: Fix string initializer code generation
      sparse, llvm: Fix global string access code generation

 sparse-llvm.c             |   16 ++++++++++++++--
 validation/backend/cast.c |    3 +++
 2 files changed, 17 insertions(+), 2 deletions(-)

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-09 11:11 Pekka Enberg [this message]
2012-06-21  9:56 ` [GIT PULL] LLVM backend updates 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=alpine.LFD.2.02.1206091408320.4769@tux.localdomain \
    --to=penberg@kernel.org \
    --cc=benh@kernel.crashing.org \
    --cc=jgarzik@redhat.com \
    --cc=linux-sparse@vger.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).