From: "Ludovic Courtès" <ludo@gnu.org>
To: Greg Hogan <code@greghogan.com>
Cc: 56666-done@debbugs.gnu.org
Subject: bug#56666: [PATCH 00/17] Add libomp per clang-toolchain.
Date: Thu, 04 Aug 2022 11:39:15 +0200 [thread overview]
Message-ID: <87les4ny9o.fsf@gnu.org> (raw)
In-Reply-To: <cover.1658327897.git.code@greghogan.com> (Greg Hogan's message of "Wed, 20 Jul 2022 14:49:06 +0000")
Hi Greg,
Greg Hogan <code@greghogan.com> skribis:
> gnu: libomp-14: Reference llvm-14 version string.
> gnu: libomp-13: Reference llvm-13 version string.
> gnu: Add libomp-12.
> gnu: clang-toolchain-12: Use libomp-12.
> gnu: Add libomp-11.
> gnu: clang-toolchain-11: Use libomp-11.
> gnu: Add libomp-10.
> gnu: clang-toolchain-10: Use libomp-10.
> gnu: Add libomp-9.
> gnu: clang-toolchain-9: Use libomp-9.
> gnu: Add libomp-8.
> gnu: clang-toolchain-8: Use libomp-8.
> gnu: Add libomp-7.
> gnu: clang-toolchain-7: Use libomp-7.
> gnu: Add libomp-6.
> gnu: clang-toolchain-6: Use libomp-6.
> gnu: make-clang-toolchain: Require explicit libomp.
Nice work! Applied, thanks.
Ludo’.
prev parent reply other threads:[~2022-08-04 9:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 14:49 [bug#56666] [PATCH 00/17] Add libomp per clang-toolchain Greg Hogan
2022-07-20 15:08 ` [bug#56666] [PATCH 01/17] gnu: libomp-14: Reference llvm-14 version string Greg Hogan
2022-07-20 15:08 ` [bug#56666] [PATCH 02/17] gnu: libomp-13: Reference llvm-13 " Greg Hogan
2022-07-20 15:08 ` [bug#56666] [PATCH 03/17] gnu: Add libomp-12 Greg Hogan
2022-07-20 15:08 ` [bug#56666] [PATCH 04/17] gnu: clang-toolchain-12: Use libomp-12 Greg Hogan
2022-07-20 15:08 ` [bug#56666] [PATCH 05/17] gnu: Add libomp-11 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 06/17] gnu: clang-toolchain-11: Use libomp-11 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 07/17] gnu: Add libomp-10 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 08/17] gnu: clang-toolchain-10: Use libomp-10 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 09/17] gnu: Add libomp-9 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 10/17] gnu: clang-toolchain-9: Use libomp-9 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 11/17] gnu: Add libomp-8 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 12/17] gnu: clang-toolchain-8: Use libomp-8 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 13/17] gnu: Add libomp-7 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 14/17] gnu: clang-toolchain-7: Use libomp-7 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 15/17] gnu: Add libomp-6 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 16/17] gnu: clang-toolchain-6: Use libomp-6 Greg Hogan
2022-07-20 15:09 ` [bug#56666] [PATCH 17/17] gnu: make-clang-toolchain: Require explicit libomp Greg Hogan
2022-08-04 9:39 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87les4ny9o.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=56666-done@debbugs.gnu.org \
--cc=code@greghogan.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).