[PATCH] gnu: LLVM, Clang, libomp, lld: Update to 18.1.5.

  • Done
  • quality assurance status badge
Details
2 participants
  • Michael Ford
  • Christopher Baines
Owner
unassigned
Submitted by
Michael Ford
Severity
normal
M
M
Michael Ford wrote on 4 May 03:11 +0200
(address . guix-patches@gnu.org)
CAFyhPjUQnAWvnQ36UZTTyMiefMxuO04RMa0NceqXeSGrQ_TpHA@mail.gmail.com
From 37410aa5b0cda9646ebf2d8a3d37e1c6ee3d17c5 Mon Sep 17 00:00:00 2001
From: fanquake <fanquake@gmail.com>
Date: Thu, 2 May 2024 12:41:59 +0800
Subject: [PATCH] gnu: LLVM, Clang, libomp, lld: Update to 18.1.5.

* gnu/packages/llvm.scm (llvm-18, clang-18, libomp-18, lld-18):
Update to 18.1.5.
---
gnu/packages/llvm.scm | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)

Toggle diff (42 lines)
diff --git a/gnu/packages/llvm.scm b/gnu/packages/llvm.scm
index 8855e1ade3..de0a46f277 100644
--- a/gnu/packages/llvm.scm
+++ b/gnu/packages/llvm.scm
@@ -551,7 +551,7 @@ (define %llvm-monorepo-hashes
("15.0.7" . "12sggw15sxq1krh1mfk3c1f07h895jlxbcifpwk3pznh4m1rjfy2")
("16.0.6" . "0jxmapg7shwkl88m4mqgfjv4ziqdmnppxhjz6vz51ycp2x4nmjky")
("17.0.6" . "1a7rq3rgw5vxm8y39fyzr4kv7w97lli4a0c1qrkchwk8p0n07hgh")
- ("18.1.4" . "1kddjysa6qj1qlb88a4m7lqni6922drgb37kj2hnspj9hrph891g")))
+ ("18.1.5" . "0n44chqn96xsa00ryhwk8g0vv3zx908xjakkgjsa14sjr9mcsq8q")))

(define %llvm-patches
'(("14.0.6" . ("clang-14.0-libc-search-path.patch"))
@@ -559,7 +559,7 @@ (define %llvm-patches
("16.0.6" . ("clang-16.0-libc-search-path.patch"))
("17.0.6" . ("clang-17.0-libc-search-path.patch"
"clang-17.0-link-dsymutil-latomic.patch"))
- ("18.1.4" . ("clang-18.0-libc-search-path.patch"
+ ("18.1.5" . ("clang-18.0-libc-search-path.patch"
"clang-17.0-link-dsymutil-latomic.patch"))))

(define (llvm-monorepo version)
@@ -1455,7 +1455,7 @@ (define-public clang-toolchain-17
(define-public llvm-18
(package
(inherit llvm-15)
- (version "18.1.4")
+ (version "18.1.5")
(source (llvm-monorepo version))))

(define-public clang-runtime-18
@@ -1471,7 +1471,7 @@ (define-public clang-18
(package-version llvm-18)))
(sha256
(base32
- "1rrf9x7n3hvzqqijfx8v8kxa2i39jdf7c164my8k6vzr7aa0dj1c")))))
+ "1azb2wn7gfpj61kh5brrima3c2lf4c9csy3xpn729zrm1n8pg8s5")))))

(define-public libomp-18
(package
--
2.45.0
C
C
Christopher Baines wrote on 19 May 14:17 +0200
(name . Michael Ford)(address . fanquake@gmail.com)(address . 70763-done@debbugs.gnu.org)
87wmnq9esd.fsf@cbaines.net
Michael Ford <fanquake@gmail.com> writes:

Toggle quote (11 lines)
> From 37410aa5b0cda9646ebf2d8a3d37e1c6ee3d17c5 Mon Sep 17 00:00:00 2001
> From: fanquake <fanquake@gmail.com>
> Date: Thu, 2 May 2024 12:41:59 +0800
> Subject: [PATCH] gnu: LLVM, Clang, libomp, lld: Update to 18.1.5.
>
> * gnu/packages/llvm.scm (llvm-18, clang-18, libomp-18, lld-18):
> Update to 18.1.5.
> ---
> gnu/packages/llvm.scm | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)

Looks good to me, I've pushed this to master now as
14176a289b29c8159cb62b1694332744a50b4679.

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

iQKlBAEBCgCPFiEEPonu50WOcg2XVOCyXiijOwuE9XcFAmZJ7eJfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDNF
ODlFRUU3NDU4RTcyMEQ5NzU0RTBCMjVFMjhBMzNCMEI4NEY1NzcRHG1haWxAY2Jh
aW5lcy5uZXQACgkQXiijOwuE9XfEdBAAmwh9WcjOkTJWRKIQFbSea0JCwkJmWJTw
HYwmHRX5AQOM0c5cjd7J5MOXD81y1BBTniq9VC6tG9kBHenGIrDE7sxgTkj3impw
YwFMGAtUXn0sPUy9nkxYGMb2Uf0Iu13KZ3Z9Lg+gF59yqHXubOH3N+uz75Ojy8uB
iwSnry2+9DgUtIvwufZDXh1dthgHE+2dchwFpw7ibVy/kDAW01Vkwiez8WXGeuyg
MpoTAw0+XSN8HpR/nGkqb4lCN9m+VlRPZpCKRTdBcU5X4LcafjENzS2CUm815myC
c0TRmxg9BwITPxA9nFRMNRdw+rm7RF2C/VrtDfvcGc/8hN5DucayJRT79Ht659jt
89C5Pxn3a9ThUXr7joGkqMS2R1H0QnPI39dXpDp513tt9dSiwp6Srk4tNZeDs36s
NbLruCpYTyyVlwhqIYIeNFKbwD9x7yRZShM6qqs2qasEOUNn8c5Q9pSVHfWsGF/e
OHBx/lImJCnXyqpyihL/L8OHiztxPbCl591kqaqvdKDfKhPOiQk1S/vVKmyXfPTK
2jDeQp+lFRf9PKj9m/mvWWSms5XWeGAF9e3s/6njBTriJ89IMIlBdy0vElo2lNOO
eWGa7AX69yBlPml1pxVdpb6z1QbwE5p0L9CQ+22t50BHCStpJwM8Ww/hmBF33r2t
iTgspAeKSIY=
=M4dX
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 70763@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 70763
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch