Re: [GIT PULL] patches for -rc3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




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

--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Newbies FAQ]     [LKML]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Trinity Fuzzer Tool]

  Powered by Linux