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

Accepted llvm-toolchain-8 1:8-2 (source) into unstable



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Wed, 20 Mar 2019 14:36:40 +0100
Source: llvm-toolchain-8
Architecture: source
Version: 1:8-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Changed-By: Gianfranco Costamagna <locutusofborg@debian.org>
Changes:
 llvm-toolchain-8 (1:8-2) unstable; urgency=medium
 .
   * Fix the search path on mips64el (which is causing the stage2
     build of mips64el to fail
     See https://bugs.llvm.org/show_bug.cgi?id=41204
 .
   [ Timo Aaltonen ]
   * import patches for intel-opencl-clang: they fix various issues
     with opengl and clang-8, and are taken from llvm master branch.
     - Fix pointer blocks on OpenCL functions, that never pointed to real
       functions
     - Fix assertion errors on some OpenCL functions
     - Refactor a little bit OpenCL calls, by emitting direct block calls.
Checksums-Sha1:
 55439d9a5508a36959d55b2fdefb97d023ed4c94 8147 llvm-toolchain-8_8-2.dsc
 fae3e5e30b794a429211997bb3b242b7a94fe928 110332 llvm-toolchain-8_8-2.debian.tar.xz
 0961949b64aa05e70d89fc40bab1b8ffb7d9d54e 23186 llvm-toolchain-8_8-2_amd64.buildinfo
Checksums-Sha256:
 55525a2f13ce13e8f058280d5e12682688cb71e69a99c9772d1c5db7ffed1e97 8147 llvm-toolchain-8_8-2.dsc
 fea02ac5d44eb20b82c2acaa011b32f9eab5d60ed988dae01ac184ae1b377e54 110332 llvm-toolchain-8_8-2.debian.tar.xz
 29af2da94f8afc64c7a2fea985309c4d1e527c26ab3a11237c2de2ed92fb6968 23186 llvm-toolchain-8_8-2_amd64.buildinfo
Files:
 2d32206f56f2c4ef4f1838ca46a32fc8 8147 devel optional llvm-toolchain-8_8-2.dsc
 88b29744c359ecb17998f759ce3f3ff0 110332 devel optional llvm-toolchain-8_8-2.debian.tar.xz
 c8f1cad20f962353f2ab1e723ab25860 23186 devel optional llvm-toolchain-8_8-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAlyiP98ACgkQfmUo2nUv
G+G+Lw/+PvmBxEmMIzEJbBpLxKPP6sCIl9sDbpEuhCBJPcwwd96JJx5TYSXLQOqD
2XnOMKx6lqEv8sdL4KeQOrjU7gMC94487ZcrtjcybNN2APBjrHJfI4biTRO21g7X
2OLGnTLrijfBa6Tb7jKRggNe+oZOSrv4DnvJKu8lIx6r9R8Dmf9beC4bRvROvamc
1YSKZWAM/GL300gfeDyiOk8Uah1/QjfGeaok1tPAKpMd2W4bDYsVtj18hfcPfBUU
53jtUavV0GAu/VN+B9tBt8gfKgfIV4pW1jMHLCWpHqzXl9jd7eFLGgMi6CvC+PZ8
KEJ94M9z1/cbuG0K8guejUdOvUj224Ij1yohlitdJxAhtTGpEZUiMW2c1TFqNxcs
BjSU4tb0WH3hQfyr7gQ9rPwzUL7OO/QUUeMEG8Vrbyw0KsMI17X+5T4AIS68HqIJ
UFTg6VfM/8+LiBgGbNU2gxrXTFl5VRF8mZ3m74w9qj1mRpuB6Ku3GcS0d7qajJnK
wwRrHFPa5jvyhIOX358zLVH44VhlIZaPFXzlJe62JTUmzPGOubRUht47GKXfULnl
LRTTqmt1td0JhpdJbSC5ocNHHU/1yjZPucq2vvHhP/ua8quc0ISJNaacFQ+r/axt
hzLJvqYq2ITLKFSD3w1fPQM9tYtQ9LDQdPGw1CSB1ff6igWkvMk=
=5UDf
-----END PGP SIGNATURE-----


Reply to: