1 |
On Mon, Jan 29, 2018 at 1:56 PM, Mick <michaelkintzios@×××××.com> wrote: |
2 |
> On Monday, 29 January 2018 18:35:58 GMT Mike Gilbert wrote: |
3 |
>> On Mon, Jan 29, 2018 at 12:50 PM, Ian Zimmerman <itz@××××××××××××.org> |
4 |
> wrote: |
5 |
>> > On 2018-01-29 20:11, Adam Carter wrote: |
6 |
>> >> Comparing the contents of |
7 |
>> >> /sys/devices/system/cpu/vulnerabilities/spectre_v2 |
8 |
>> >> |
9 |
>> >> With gcc 7.2 + kernel 4.14.15; |
10 |
>> >> Intel system shows; Vulnerable: Minimal generic ASM retpoline |
11 |
>> >> AMD system shows: Vulnerable: Minimal AMD ASM retpoline |
12 |
>> >> |
13 |
>> >> With gcc 7.3 + kernel 4.15.0; |
14 |
>> >> Intel system shows; Mitigation: Full generic retpoline |
15 |
>> >> AMD system shows' Mitigation: Full AMD retpoline |
16 |
>> > |
17 |
>> > Is there a simple way, with the upstream (kernel.org) sources, to force |
18 |
>> > a compiler different from the system default? If there is, it's not in |
19 |
>> > the |
20 |
>> > README, and a simple grep over the Makefiles also doesn't enlighten. |
21 |
>> > |
22 |
>> > I am not ready to activate a keyworded gcc for general use. |
23 |
>> |
24 |
>> You could pass CC=gcc-7.3.0 to the make command, like so: |
25 |
>> |
26 |
>> make -j6 CC=gcc-7.3.0 |
27 |
> |
28 |
> Shouldn't you have at least compiled your whole toolchain with gcc-7.3.0 |
29 |
> first? |
30 |
|
31 |
I don't see any reason that would be necessary. |