public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "noloader at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/68081] Cygwin GCC cannot compile program that uses __builtin_ia32_rdseed64_step
Date: Sat, 24 Oct 2015 21:11:00 -0000	[thread overview]
Message-ID: <bug-68081-4-w7iWLJqvIO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68081-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68081

--- Comment #3 from Jeffrey Walton <noloader at gmail dot com> ---
(In reply to Jeffrey Walton from comment #2)
> (In reply to Andrew Pinski from comment #1)
> > Why are you using the builtin directly?  You should be using the intrinsics
> > form instead.
> 
> Its a cross product of (1) that's what the docs tell me to use for RDRAND
> and (2) lack of documentation for RDSEED.
> 
> The doc I am referring to is
> http://gcc.gnu.org/onlinedocs/gcc/x86-Built-in-Functions.html#x86-Built-in-
> Functions lists. It tells me to use "__builtin_ia32_rdrand{16|32|64}_step"
> for RDRAND. But it does not tell me what to use for RDSEED. I made the leap
> I should use the *_rdseed variants for RDSEED.
> 
> (My apologies for the literal read. If I should be doing something
> different, then I need to be told to do so :)

By the way, I tried to find RDRAND and RDSEED intrinsic functions in the past:
http://www.google.com/search?q=RDRAND+intrinsic+site:gnu.org . The best I can
tell, they are undocumented.

I did find H.J. Lu's patches that provide __builtin_ia32_rdseed{X}_step, so I
used them instead. They are documented, so I used them.

Its very important (to me) to find provenance in vendor documentation.


  parent reply	other threads:[~2015-10-24 21:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-24 20:38 [Bug c/68081] New: " noloader at gmail dot com
2015-10-24 20:52 ` [Bug target/68081] " pinskia at gcc dot gnu.org
2015-10-24 20:58 ` noloader at gmail dot com
2015-10-24 21:11 ` noloader at gmail dot com [this message]
2015-10-25  8:09 ` glisse at gcc dot gnu.org
2015-10-25 10:44 ` noloader at gmail dot com
2015-10-25 12:08 ` glisse at gcc dot gnu.org
2015-10-25 12:39 ` noloader at gmail dot com
2021-04-03 10:22 ` redi at gcc dot gnu.org

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=bug-68081-4-w7iWLJqvIO@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).