public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lh_mouse at 126 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/105764] New: libgfortran fails to build with a custom thread model
Date: Sun, 29 May 2022 03:33:55 +0000 [thread overview]
Message-ID: <bug-105764-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105764
Bug ID: 105764
Summary: libgfortran fails to build with a custom thread model
Product: gcc
Version: 12.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libfortran
Assignee: unassigned at gcc dot gnu.org
Reporter: lh_mouse at 126 dot com
Target Milestone: ---
Created attachment 53049
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53049&action=edit
proposed patch
Bootstrapping GCC with fortran enabled and a custom thread model can fail:
```
In file included from ../../../gcc/libgfortran/runtime/error.c:28:
../../../gcc/libgfortran/io/async.h:354:3: error: unknown type name 'pthread_t'
354 | pthread_t thread;
| ^~~~~~~~~
```
In commit a79878585a1c5e32bafbc6d1e73f91fd6e4293bf, `pthread_mutex_t` was
replaced with `__gthread_mutex_t`, but `pthread_t` was left over. Not sure
whether this was by design, or was an oversight.
Patch also sent to gcc-patches:
https://gcc.gnu.org/pipermail/gcc-patches/2022-May/595754.html
next reply other threads:[~2022-05-29 3:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 3:33 lh_mouse at 126 dot com [this message]
2022-10-09 16:50 ` [Bug libfortran/105764] " egallager at gcc dot gnu.org
2022-10-10 7:26 ` lh_mouse at 126 dot com
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-105764-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).