From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] kvm-unit-test: revert use of RDSEED and RDRAND
Date: Thu, 4 Jan 2018 09:36:57 +0100 [thread overview]
Message-ID: <20180104093657.40b45c55@windsurf.lan> (raw)
In-Reply-To: <CANQCQpaEF6aZKx8FWFNsctjvugx=zsM_Fc0c7ODDtvknLYOQVQ@mail.gmail.com>
Hello,
On Wed, 3 Jan 2018 16:42:34 -0600, Matthew Weber wrote:
> Yeah, I've done the research but was still looking at how. Here's
> where I was at below.......
>
> I'd default to disable because we don't have any way to tell what the
> end processor is for execution of what we build. Worst case we could
> use the cpu type and enable a new configure option to turn this
> feature on/off. I can suggest that to the mailing list and maybe
> they'd be ok with it defaulting to on.
Well, gcc/binutils will barf out with an error if the selected
processor variant (via mcpu) doesn't support the instruction.
Of course, if you specify a bogus mcpu flag that doesn't match your
target CPU, then it won't run. But well, passing a bogus mcpu is
already going to generate code that won't run: if you build for core-i7
and run on your old i486, the code won't run.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2018-01-04 8:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 4:36 [Buildroot] [PATCH] kvm-unit-test: revert use of RDSEED and RDRAND Matt Weber
2017-12-14 8:44 ` Thomas Petazzoni
2017-12-15 20:41 ` Matthew Weber
2017-12-15 20:41 ` [Buildroot] FW: " Kees van Unen
2017-12-18 7:49 ` [Buildroot] " Thomas Petazzoni
2018-01-03 22:27 ` Thomas Petazzoni
2018-01-03 22:42 ` Matthew Weber
2018-01-04 8:36 ` Thomas Petazzoni [this message]
2018-01-09 16:09 ` Matthew Weber
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=20180104093657.40b45c55@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 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.