public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libfortran/105764] New: libgfortran fails to build with a custom thread model
@ 2022-05-29 3:33 lh_mouse at 126 dot com
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
0 siblings, 2 replies; 3+ messages in thread
From: lh_mouse at 126 dot com @ 2022-05-29 3:33 UTC (permalink / raw)
To: gcc-bugs
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libfortran/105764] libgfortran fails to build with a custom thread model
2022-05-29 3:33 [Bug libfortran/105764] New: libgfortran fails to build with a custom thread model lh_mouse at 126 dot com
@ 2022-10-09 16:50 ` egallager at gcc dot gnu.org
2022-10-10 7:26 ` lh_mouse at 126 dot com
1 sibling, 0 replies; 3+ messages in thread
From: egallager at gcc dot gnu.org @ 2022-10-09 16:50 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105764
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
CC| |aldot at gcc dot gnu.org,
| |egallager at gcc dot gnu.org
Last reconfirmed| |2022-10-09
Assignee|unassigned at gcc dot gnu.org |lh_mouse at 126 dot com
--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
Taking conversation on the gcc-patches mailing list as confirmation:
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/602821.html
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libfortran/105764] libgfortran fails to build with a custom thread model
2022-05-29 3:33 [Bug libfortran/105764] New: libgfortran fails to build with a custom thread model lh_mouse at 126 dot com
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
1 sibling, 0 replies; 3+ messages in thread
From: lh_mouse at 126 dot com @ 2022-10-10 7:26 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105764
LIU Hao <lh_mouse at 126 dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from LIU Hao <lh_mouse at 126 dot com> ---
This has been fixed on trunk with decbb5bf7cc7317fefa53f0d64082cf020e85e42.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-10-10 7:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-05-29 3:33 [Bug libfortran/105764] New: libgfortran fails to build with a custom thread model lh_mouse at 126 dot com
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
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).