public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Gary.White at ColoState dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/106509] New: executable hangs if -static is included in compile
Date: Tue, 02 Aug 2022 19:22:06 +0000 [thread overview]
Message-ID: <bug-106509-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106509
Bug ID: 106509
Summary: executable hangs if -static is included in compile
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: Gary.White at ColoState dot edu
Target Milestone: ---
Created attachment 53398
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53398&action=edit
gfortran code to reproduce this bug
When the attached code is compiled as:
gfortran bug.f90 -fopenmp -o bug.exe -static
the executable hangs even with a STOP message shown.
If -static is removed, the code executes.
Also, if the number of threads specified is equal to the number available, the
code executes with -static . But the combination of -static and fewer threads
specified than available on the machine causes the code to hang.
This bug only occurs with gfortran 12.1. The identical code compiled with
gfortran 11 does not hang.
next reply other threads:[~2022-08-02 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 19:22 Gary.White at ColoState dot edu [this message]
2022-08-02 19:38 ` [Bug fortran/106509] " pinskia at gcc dot gnu.org
2022-08-02 19:44 ` [Bug libfortran/106509] " Gary.White at ColoState dot edu
2022-08-02 22:59 ` kargl 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-106509-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).