public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pexu@gcc-bugzilla.mail.kapsi.fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/102408] New: [OpenACC] omp-oacc-neuter-broadcast.cc: random() not available on all platforms
Date: Mon, 20 Sep 2021 12:11:31 +0000	[thread overview]
Message-ID: <bug-102408-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102408
           Summary: [OpenACC] omp-oacc-neuter-broadcast.cc: random() not
                    available on all platforms
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pexu@gcc-bugzilla.mail.kapsi.fi
  Target Milestone: ---
              Host: x86_64-linux-gnu
            Target: x86_64-w64-mingw32

Hi.

random() is not available on all platforms (it's XSI), e.g. mingw.

I wonder if the simplest thing would be simply to use rand() or std::rand()
given that the required random value is quite small?

<...>/gcc/omp-oacc-neuter-broadcast.cc: In function 'void
oacc_do_neutering(long long unsigned int, long long unsigned int)':
<...>/gcc/omp-oacc-neuter-broadcast.cc:1786:23: error: 'random' was not
declared in this scope; did you mean 'rand'?
 1786 |    base = bounds_lo + random () % 512;

The problematic commit:
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=2a3f9f6532bb21d8ab6f16fbe9ee603f6b1405f2

             reply	other threads:[~2021-09-20 12:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20 12:11 pexu@gcc-bugzilla.mail.kapsi.fi [this message]
2021-09-20 19:46 ` [Bug other/102408] " tschwinge at gcc dot gnu.org
2021-09-21 10:39 ` cvs-commit at gcc dot gnu.org
2021-09-21 10:45 ` tschwinge 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-102408-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).