public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "罗百科" <patrick@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lang/ispc/
Date: Thu, 20 Jan 2022 07:41:17 +0000 (UTC)	[thread overview]
Message-ID: <1642664476.63fc3db3d1b9ac9d31c76f496144529ac947e07a.patrick@gentoo> (raw)

commit:     63fc3db3d1b9ac9d31c76f496144529ac947e07a
Author:     Patrick Lauer <patrick <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 20 07:40:58 2022 +0000
Commit:     罗百科 <patrick <AT> gentoo <DOT> org>
CommitDate: Thu Jan 20 07:41:16 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=63fc3db3

dev-lang/ispc: Allow llvm-13 for ispc-1.17

Thanks to Marcos Rodrigues Gonzalez for testing and reporting.
Upstream is officially still on 12, but it builds and tests pass.

Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Patrick Lauer <patrick <AT> gentoo.org>

 dev-lang/ispc/{ispc-1.17.0.ebuild => ispc-1.17.0-r1.ebuild} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-lang/ispc/ispc-1.17.0.ebuild b/dev-lang/ispc/ispc-1.17.0-r1.ebuild
similarity index 98%
rename from dev-lang/ispc/ispc-1.17.0.ebuild
rename to dev-lang/ispc/ispc-1.17.0-r1.ebuild
index a0b5d2d84d28..1856351fc963 100644
--- a/dev-lang/ispc/ispc-1.17.0.ebuild
+++ b/dev-lang/ispc/ispc-1.17.0-r1.ebuild
@@ -4,7 +4,7 @@
 EAPI=7
 
 PYTHON_COMPAT=( python3_{8..10} )
-LLVM_MAX_SLOT=12
+LLVM_MAX_SLOT=13
 inherit cmake python-any-r1 llvm
 
 DESCRIPTION="Intel SPMD Program Compiler"


             reply	other threads:[~2022-01-20  7:41 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20  7:41 罗百科 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-06  4:10 [gentoo-commits] repo/gentoo:master commit in: dev-lang/ispc/ Michał Górny
2024-11-23 17:23 Michał Górny
2024-11-23 17:21 Michał Górny
2024-11-08  4:52 Michał Górny
2024-11-02  7:14 Michał Górny
2024-11-02  6:32 Michał Górny
2024-11-02  6:32 Michał Górny
2024-10-17  2:51 Michał Górny
2024-10-15  7:00 Michał Górny
2024-06-15 13:08 Michał Górny
2024-06-15 10:54 Arthur Zamarin
2024-05-23  2:11 Michał Górny
2024-03-10  3:35 Michał Górny
2024-03-09 21:10 Sam James
2024-02-16  5:40 Michał Górny
2024-01-25  3:14 Sam James
2023-12-31 15:30 Michał Górny
2023-12-31 14:56 Michał Górny
2023-12-31 10:07 Michał Górny
2023-12-31  9:57 Michał Górny
2023-12-31  9:57 Michał Górny
2023-10-19 15:13 Michał Górny
2023-06-12 15:44 Sam James
2023-02-26  8:27 罗百科
2023-01-26 20:51 Andreas Sturmlechner
2023-01-08 16:04 Joonas Niilola
2022-12-24 14:03 Andreas Sturmlechner
2022-12-24 14:01 Andreas Sturmlechner
2022-12-19 14:47 Andreas Sturmlechner
2022-10-13 10:31 Ionen Wolkens
2022-07-19  7:47 Michał Górny
2022-05-20 13:21 Joonas Niilola
2022-05-20 11:25 Joonas Niilola
2022-04-25  2:40 Sam James
2022-01-19  7:32 罗百科
2021-11-07 11:38 Jakov Smolić
2021-10-31  5:53 Sam James
2021-10-20  4:11 Sam James
2021-09-19  3:30 Sam James
2021-09-19  3:09 Sam James
2021-09-19  3:09 Sam James
2021-06-19 23:23 Ionen Wolkens
2021-06-19 23:23 Ionen Wolkens
2020-12-09  9:42 Joonas Niilola
2020-09-10  3:18 Sam James
2020-09-10  2:16 Sam James
2020-09-10  1:18 Sam James
2020-09-10  1:18 Sam James
2020-09-10  1:18 Sam James
2020-09-10  1:18 Sam James
2020-09-10  0:42 Sam James
2020-09-10  0:42 Sam James
2020-07-29 16:52 Andreas Sturmlechner
2018-04-11 16:19 Michał Górny
2018-04-04 13:17 Christoph Junghans
2017-09-29 22:40 Christoph Junghans
2017-07-30  8:47 Michał Górny
2017-03-19 14:06 Christoph Junghans
2016-07-13 15:26 Christoph Junghans
2016-07-13 15:26 Christoph Junghans
2016-07-12 19:31 Christoph Junghans
2016-05-30 20:11 Christoph Junghans
2016-05-30 20:11 Christoph Junghans
2015-10-20 23:27 Christoph Junghans
2015-10-20 16:01 Christoph Junghans
2015-10-07 15:59 Christoph Junghans
2015-10-07 15:59 Christoph Junghans

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=1642664476.63fc3db3d1b9ac9d31c76f496144529ac947e07a.patrick@gentoo \
    --to=patrick@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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