From: Efraim Flashner <efraim@flashner.co.il>
To: Zheng Junjie <zhengjunjie@iscas.ac.cn>
Cc: 71804-done@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#71804: [PATCH 0/4] gcc-14
Date: Tue, 2 Jul 2024 13:21:10 +0300 [thread overview]
Message-ID: <ZoPUlg9npWm4lDkG@3900XT> (raw)
In-Reply-To: <cover.1719502347.git.zhengjunjie@iscas.ac.cn>
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
On Thu, Jun 27, 2024 at 11:35:58PM +0800, Zheng Junjie wrote:
> This patchset add gcc 14.
>
> Miss compiler-cpu-architectures because i not sure how to add them.
Shouldn't be a problem. For now they'll just inherit from gcc-13.
I checked gccgo-14 and it seems it still does provide go-1.18. I was
hoping they'd have synced with golang and had a more recent version.
Patches pushed! Thanks.
> Zheng Junjie (4):
> gnu: Add gcc-14.
> gnu: Add gccgo-14.
> gnu: Add gcc-toolchain-14.
> gnu: Add libgccjit-14.
>
> gnu/packages/commencement.scm | 3 +++
> gnu/packages/gcc.scm | 29 +++++++++++++++++++++++++++++
> 2 files changed, 32 insertions(+)
>
>
> base-commit: 97540acadc4d275cfe50ba75f2dc0122276da30d
> --
> 2.41.0
>
>
>
>
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-07-02 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 15:35 [bug#71804] [PATCH 0/4] gcc-14 Zheng Junjie
2024-06-27 15:38 ` [bug#71804] [PATCH 1/4] gnu: Add gcc-14 Zheng Junjie
2024-06-27 15:38 ` [bug#71804] [PATCH 2/4] gnu: Add gccgo-14 Zheng Junjie
2024-06-27 15:38 ` [bug#71804] [PATCH 3/4] gnu: Add gcc-toolchain-14 Zheng Junjie
2024-06-27 15:38 ` [bug#71804] [PATCH 4/4] gnu: Add libgccjit-14 Zheng Junjie
2024-07-02 10:21 ` Efraim Flashner [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZoPUlg9npWm4lDkG@3900XT \
--to=efraim@flashner.co.il \
--cc=71804-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=zhengjunjie@iscas.ac.cn \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.