From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>
Subject: Re: [GIT PULL] patches for -rc3
Date: Wed, 21 Jun 2017 21:42:26 +0100 [thread overview]
Message-ID: <8f6e37dc-ae7a-deb2-e804-10b9d0e81cf6@ramsayjones.plus.com> (raw)
In-Reply-To: <20170621135831.h27ixpxbqdlvlhtn@ltop.local>
On 21/06/17 14:58, Luc Van Oostenryck wrote:
> Chris,
>
> Please pull these patches for v0.5.1-rc3.
> The patches of two kinds:
> *) fixes for problem found during pre-release testing:
> - missing examine in evaluate_dereference()
> - workaround for bogus phi-nodes
> - fix for OP_PHI liveness
> - fix for __builtin_bswap{16,32,64}() constantness
> *) small things inhibiting testing:
> - dissect: use built_in_ident() instead of MK_IDENT()
> - little/big-endian flag & defines
> - cgcc support for arm, arm64 & ppc64
>
>
> Everything have now been tested on:
> - linux i386, x86-64, arm64, arm, ppc64 & ppc64le
> - freebsd x86-64
> - openbsd i386 (llvm backend not tested)
> - darwin x86-64
> and the tests consisted in:
> - sparse's testsuite, of course,
> - on linux, a kernel compile for an allyesconfig and looking
> after some oddities in the logs, like a crash or an unusal
> warning.
> - doing a 'make sparse' on the git's tree
>
> The only remaining problem I saw was a failire in the llvm
> backend on arm (but I only had a rather old version of LLVM).
>
> Unless a last minute problem, this should be the last patches
> for the release.
>
> Regards,
> Luc
>
> ----------------------------------------------------------------
>
> The following changes since commit bcfe020ed939fa1e8474efaf31a86d80d0e5c5fe:
>
> add support for -fmemcpy-max-count (2017-06-15 10:03:49 +0200)
>
> are available in the git repository at:
>
> git://github.com/lucvoo/sparse.git tags/for-chris
>
> for you to fetch changes up to a6fbbbf01a1ca358e0a991dd0fb1a1cca60b6f0b:
>
> bump sparse's version to -rc3 (2017-06-21 15:30:04 +0200)
Tested on Linux (i686 and x86_64) and cygwin (x86_64).
Both the sparse testsuite and 'make sparse' on the git tree
work as expected, without additional failures.
Thanks!
ATB,
Ramsay Jones
next prev parent reply other threads:[~2017-06-21 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 13:58 [GIT PULL] patches for -rc3 Luc Van Oostenryck
2017-06-21 20:42 ` Ramsay Jones [this message]
2017-06-21 20:54 ` Luc Van Oostenryck
2017-06-22 2:00 ` Christopher Li
2017-06-22 5:20 ` 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=8f6e37dc-ae7a-deb2-e804-10b9d0e81cf6@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.com \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox