public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/98301] random_init() is broken
Date: Mon, 22 Feb 2021 19:11:46 +0000 [thread overview]
Message-ID: <bug-98301-4-g9eMvrNv68@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98301-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98301
--- Comment #7 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Mon, Feb 22, 2021 at 06:57:03PM +0000, sgk at troutmask dot
apl.washington.edu wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98301
>
> --- Comment #6 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
> On Mon, Feb 22, 2021 at 04:36:50AM +0000, jvdelisle at gcc dot gnu.org wrote:
> >
> > --- Comment #5 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
> > Steve, if you think this does it. I will get it ready to commit for you. Does
> > it also need to be back ported?
> >
>
> Well, I think it is correct for at least what I've been
> able to test! I don't use co-arrays, so do not have
> OpenCoarray or the shared-memory WIP installed. For,
> -fcoarray=lib or -fcoarray=shared, function calls are
> generated. These are currently unimplimented and need
> to be implemented in such a manner as the function calls
> are aware of the underlying coarray implemention. I
> don't remember the details, but I recall that the images
> need to communicate about the seeds.
>
Oh, one last item. This patch will likely break gfortran+opencoarray
because _gfortran_caf_random_init is missing, and therefore will
prevent linking of the program.
next prev parent reply other threads:[~2021-02-22 19:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 20:15 [Bug libfortran/98301] New: random_init() may be non-conforming kargl at gcc dot gnu.org
2020-12-15 20:17 ` [Bug libfortran/98301] " kargl at gcc dot gnu.org
2020-12-15 20:17 ` kargl at gcc dot gnu.org
2020-12-15 20:18 ` kargl at gcc dot gnu.org
2020-12-18 4:01 ` [Bug libfortran/98301] random_init() is broken kargl at gcc dot gnu.org
2020-12-21 0:53 ` kargl at gcc dot gnu.org
2021-02-22 4:36 ` jvdelisle at gcc dot gnu.org
2021-02-22 18:57 ` sgk at troutmask dot apl.washington.edu
2021-02-22 19:11 ` sgk at troutmask dot apl.washington.edu [this message]
2021-04-03 17:00 ` kargl at gcc dot gnu.org
2021-04-23 7:15 ` vehre at gcc dot gnu.org
2021-04-26 10:37 ` vehre at gcc dot gnu.org
2021-04-26 10:38 ` vehre at gcc dot gnu.org
2021-05-22 11:30 ` cvs-commit at gcc dot gnu.org
2021-05-22 11:45 ` vehre at gcc dot gnu.org
2021-06-06 10:13 ` cvs-commit at gcc dot gnu.org
2021-09-17 6:47 ` pinskia 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-98301-4-g9eMvrNv68@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).