public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: gcc 7.3 + kernel 4.15 = spectre_v2 fixed
Date: Mon, 29 Jan 2018 20:35:29 +0200	[thread overview]
Message-ID: <CAJ1xhMVakY6HNOQn+1Q+xDeDAb-dv_DQbJxnxraZwoGg4sdSTw@mail.gmail.com> (raw)
In-Reply-To: <20180129175038.j3fsam5dlxszkcl2@matica.foolinux.mooo.com>

On Mon, Jan 29, 2018 at 7:50 PM, Ian Zimmerman <itz@very.loosely.org> wrote:
> On 2018-01-29 20:11, Adam Carter wrote:
>
>> Comparing the contents of /sys/devices/system/cpu/vulnerabilities/spectre_v2
>>
>> With gcc 7.2 + kernel 4.14.15;
>> Intel system shows; Vulnerable: Minimal generic ASM retpoline
>> AMD system shows: Vulnerable: Minimal AMD ASM retpoline
>>
>> With gcc 7.3 + kernel 4.15.0;
>> Intel system shows; Mitigation: Full generic retpoline
>> AMD system shows' Mitigation: Full AMD retpoline
>
> Is there a simple way, with the upstream (kernel.org) sources, to force
> a compiler different from the system default?  If there is, it's not in the
> README, and a simple grep over the Makefiles also doesn't enlighten.
>
> I am not ready to activate a keyworded gcc for general use.
>
> --
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet, fetch the TXT record for the domain.
>

To compile the kernel with a different compiler, the method shown
below may be used, e.g.:
make CC=clang

See [1], for details:
Building the kernel with Clang:
[1] https://lwn.net/Articles/734071/


  reply	other threads:[~2018-01-29 18:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29  9:11 [gentoo-user] gcc 7.3 + kernel 4.15 = spectre_v2 fixed Adam Carter
2018-01-29 17:50 ` [gentoo-user] " Ian Zimmerman
2018-01-29 18:35   ` Alexander Kapshuk [this message]
2018-01-30 21:20     ` Ian Zimmerman
2018-01-29 18:35   ` Mike Gilbert
2018-01-29 18:56     ` Mick
2018-01-29 19:32       ` Mike Gilbert
2018-01-29 22:36 ` [gentoo-user] " Henry Kohli
2018-01-30  4:35   ` [gentoo-user] " Nikos Chantziaras
2018-01-30 21:43     ` Rich Freeman
2018-01-31  9:16       ` Nikos Chantziaras
2018-01-31  9:48         ` Taiidan
2018-01-31 10:22           ` Nikos Chantziaras
2018-01-31 11:30             ` Martin Vaeth
2018-01-31 12:04               ` Mick
2018-01-31 12:20                 ` Nikos Chantziaras
2018-01-31 12:38                   ` Mick
2018-02-02 11:19                   ` Mick
2018-02-03  8:14                     ` Nikos Chantziaras
2018-01-31 11:17         ` Martin Vaeth
2018-01-31 12:07           ` Nikos Chantziaras
2018-01-31 13:23             ` Martin Vaeth
2018-01-31 14:34             ` Rich Freeman
2018-01-31 14:24         ` Rich Freeman

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=CAJ1xhMVakY6HNOQn+1Q+xDeDAb-dv_DQbJxnxraZwoGg4sdSTw@mail.gmail.com \
    --to=alexander.kapshuk@gmail.com \
    --cc=gentoo-user@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