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 c/68081] New: Cygwin GCC cannot compile program that uses __builtin_ia32_rdseed64_step
Date: Sat, 24 Oct 2015 20:38:00 -0000	[thread overview]
Message-ID: <bug-68081-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 68081
           Summary: Cygwin GCC cannot compile program that uses
                    __builtin_ia32_rdseed64_step
           Product: gcc
           Version: 5.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: noloader at gmail dot com
  Target Milestone: ---

I'm testing on Cygwin64. Cygwin64 provides the 5.2.0 compiler.

Attempting to compile the following results in an error:

  $ cat rdseed.c
  #include <stdint.h>

  int main()
  {
    uint64_t val;
    __builtin_ia32_rdseed64_step(&val);
    return (int)val;
  }

The error is:

  $ gcc -mrdseed rdseed.c -o rdseed.exe
  ...
  rdseed.c:6:36: error: '__builtin_ia32_rdseed64_step' was not declared in this
scope.

The expected define appears to be defined:

  $ cpp -mrdseed -dM </dev/null | grep -i seed
  #define __RDSEED__ 1

The RDRAND equivalent compiles and executes.

-----

My apologies if this should be reported to Cygwin. I cannot find their bug
reporter. In fact, I can't even find a mailing list to discuss it. Their
mailing list page tells me where *not* to discuss or report bugs, but does not
state where to discuss or report them.


             reply	other threads:[~2015-10-24 20:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-24 20:38 noloader at gmail dot com [this message]
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
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@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).