public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/99171] [10 Regression] Optional procedure call inside Open MP parallel loop produces Segmentation Fault
Date: Sat, 20 Feb 2021 12:22:35 +0000 [thread overview]
Message-ID: <bug-99171-4-vUQ0nr49Kw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99171-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99171
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-02-20
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed on GCC10 and 11. With GCC9 the run time give
When optional function is called without Open MP directive:
Printing Something
When optional function is called inside Open MP directive:
Printing Something
Printing Something
Printing Something
Printing Something
Printing Something
Printing Something
Printing Something
Printing Something
Printing Something
Printing Something
Printing Something
Printing Something
Printing Something
Printing Something
Printing Something
Printing Something
next prev parent reply other threads:[~2021-02-20 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-19 20:32 [Bug fortran/99171] New: " am41119 at hotmail dot com
2021-02-20 12:22 ` dominiq at lps dot ens.fr [this message]
2021-02-20 12:23 ` [Bug fortran/99171] [10/11 " dominiq at lps dot ens.fr
2021-02-22 8:40 ` rguenth at gcc dot gnu.org
2021-02-22 12:20 ` cvs-commit at gcc dot gnu.org
2021-02-22 14:01 ` cvs-commit at gcc dot gnu.org
2021-02-22 14:03 ` [Bug fortran/99171] [10/11 Regression] Optional procedure call inside OpenMP " burnus at gcc dot gnu.org
2021-02-22 14:03 ` burnus 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-99171-4-vUQ0nr49Kw@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).