From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCHES] gnu: linux-libre: Full retpoline support on x86 [spectre mitigation]
Date: Sat, 27 Jan 2018 16:33:34 +0100 [thread overview]
Message-ID: <87o9lf2u5t.fsf@gnu.org> (raw)
In-Reply-To: <87po648e2n.fsf@netris.org> (Mark H. Weaver's message of "Sat, 20 Jan 2018 15:34:08 -0500")
Hi Mark,
Mark H Weaver <mhw@netris.org> skribis:
> Here are two patches that:
>
> * Add gcc-7.3.0-RC-20180117, which includes support for retpoline.
> * Use gcc-7.3 to build linux-libre on x86 systems.
With GCC 7.3.0 now out, I think you can go ahead.
> From 387a02c3f9e157bdf40b2b5ad0e53e5b209f3aa5 Mon Sep 17 00:00:00 2001
> From: Mark H Weaver <mhw@netris.org>
> Date: Sat, 20 Jan 2018 15:15:19 -0500
> Subject: [PATCH 1/2] gnu: gcc: Add gcc 7.3.0-RC-20180117 [includes retpoline
> support].
>
> * gnu/packages/gcc.scm (gcc-7.3): New variable.
I think we can upgrade ‘gcc-7’ directly instead of introducing a new
‘gcc-7.3’ variable. Thoughts?
> --- a/gnu/packages/linux.scm
> +++ b/gnu/packages/linux.scm
> @@ -283,6 +283,12 @@ for ARCH and optionally VARIANT, or #f if there is no such configuration."
> ("bc" ,bc)
> ("openssl" ,openssl)
> ("kmod" ,kmod)
> + ,@(match (system->linux-architecture
> + (or (%current-target-system) (%current-system)))
> + ((or "x86_64" "i386")
> + `(("gcc" ,gcc-7.3)))
Perhaps add a comment that this is for the retpoline mitigation.
Otherwise LGTM, thank you!
Ludo’.
next prev parent reply other threads:[~2018-01-27 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 20:34 [PATCHES] gnu: linux-libre: Full retpoline support on x86 [spectre mitigation] Mark H Weaver
2018-01-22 6:09 ` Chris Marusich
2018-01-22 20:51 ` Leo Famulari
2018-01-22 13:18 ` Alex Vong
2018-01-26 11:41 ` Alex Vong
2018-01-23 21:04 ` Leo Famulari
2018-01-27 15:33 ` Ludovic Courtès [this message]
2018-01-27 20:01 ` Mark H Weaver
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=87o9lf2u5t.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.
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.