From: Dan Gora <dg@adax.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Sanford, Robert" <rsanford@akamai.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: meson options - build vs target machine cpuflags question
Date: Thu, 10 Mar 2022 23:45:39 -0300 [thread overview]
Message-ID: <CAGyogRbbr_+Y2GwDk+rR7noS=xEW5wHF-CqmGOv51yeDTdnYNw@mail.gmail.com> (raw)
In-Reply-To: <20220310171854.272f459b@hermes.local>
On Thu, Mar 10, 2022 at 10:19 PM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> The ideal solution would be able to use gcc function attributes and dyanmic
> linking to do this at runtime - ie multiversion library. But this opens a set
> of different problems like compiler versions and testing.
Detecting RDSEED at run time doesn't require any of that, but working
around the possible absence of getentropy() does. However none of my
proposed solutions, including dynamic linking was deemed suitable.. or
something, so I gave up.
next prev parent reply other threads:[~2022-03-11 2:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 14:46 Sanford, Robert
2022-03-10 22:54 ` Dan Gora
2022-03-10 22:58 ` Dan Gora
2022-03-10 23:39 ` Sanford, Robert
2022-03-11 0:00 ` Dan Gora
2022-03-11 1:18 ` Stephen Hemminger
2022-03-11 2:45 ` Dan Gora [this message]
2022-03-11 3:01 ` Stephen Hemminger
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='CAGyogRbbr_+Y2GwDk+rR7noS=xEW5wHF-CqmGOv51yeDTdnYNw@mail.gmail.com' \
--to=dg@adax.com \
--cc=rsanford@akamai.com \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.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;
as well as URLs for NNTP newsgroup(s).