From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Spectre-NG
Date: Wed, 9 May 2018 20:04:05 +0100 [thread overview]
Message-ID: <5AF34625.9010708@youngman.org.uk> (raw)
In-Reply-To: <slrnpf6ev3.hum.martin@clover.invalid>
On 09/05/18 19:18, Martin Vaeth wrote:
> As mentioned, I wonder why gcc/clang do not yet support this
> horribly slow but spectre-safe option. It can't be that hard to
> implement in the actual code-producing back-end.
Given the response by the gcc team to security people complaining that
gcc was optimising out security-sensitive code (namely, a two-fingered
salute near enough), I doubt the gcc team would have any interest in
optimisations that SLOWED DOWN the resultant code.
I suspect that might be one of the forces driving the kernel towards
CLANG - a development team that is not obsessed with performance at the
expense of breaking any code that uses undefined features.
Unfortunately, when dealing with hardware, one is forced to rely on
undefined features. A strong point of C, until the compiler decides to
go "rogue" on you ...
Cheers,
Wol
next prev parent reply other threads:[~2018-05-09 19:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 11:15 [gentoo-user] Spectre-NG Mick
2018-05-07 11:45 ` Rich Freeman
2018-05-08 8:19 ` [gentoo-user] Spectre-NG Martin Vaeth
2018-05-08 20:15 ` Rich Freeman
2018-05-09 18:18 ` Martin Vaeth
2018-05-09 19:04 ` Wols Lists [this message]
2018-05-09 22:50 ` Ian Zimmerman
2018-05-10 13:35 ` Wol's lists
2018-05-10 16:52 ` Ian Zimmerman
2018-05-09 19:16 ` Rich Freeman
2018-05-10 5:34 ` Martin Vaeth
2018-05-10 13:58 ` Rich Freeman
2018-05-10 15:31 ` Martin Vaeth
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=5AF34625.9010708@youngman.org.uk \
--to=antlists@youngman.org.uk \
--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