From: LIU Hao <lh_mouse@126.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
LIU Hao via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: fortran@gcc.gnu.org
Subject: Re: Adding a new thread model to GCC
Date: Sun, 2 Oct 2022 20:54:54 +0800 [thread overview]
Message-ID: <7c519f0b-2a6d-e9bf-993a-2eff2cdad418@126.com> (raw)
In-Reply-To: <7116A6F3-3968-4720-A65C-FFB05BFE181D@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 936 bytes --]
在 2022-10-02 04:02, Bernhard Reutner-Fischer 写道:
> On 1 October 2022 20:34:45 CEST, LIU Hao via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>> Greetings.
>
>> The first patch is necessary because somewhere in libgfortran, `pthread_t` is referenced. If the thread model is not `posix`, it fails to compile.
>
> One of several shortcomings mentioned already on Sun, 02 Sep 2018 15:40:28 -0700 in
> https://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg196212.html
>
Forgive me but I didn't get your point. Is the 'shortcoming' the fact that `pthread_t` must be
preferred to `__gthread_t`?
For non-posix thread models, <pthread.h> is not included, so `pthread_t` is not declared. I haven't
looked at other code in libgfortran, but changing `pthread_t` to `__gthread_t` does allow
libgfortran to build. I don't know how to test it though, as I don't write Fortran myself.
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-10-02 12:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0f1f223a-3756-1da3-bd1d-b87edd34e1f9@126.com>
2022-10-01 20:02 ` Bernhard Reutner-Fischer
2022-10-02 12:54 ` LIU Hao [this message]
2022-10-03 5:03 ` Bernhard Reutner-Fischer
2022-10-04 8:06 ` LIU Hao
2022-10-04 19:45 ` Bernhard Reutner-Fischer
[not found] ` <21655510.EfDdHjke4D@fomalhaut>
[not found] ` <CACb0b4nhp89FmAHkuYEZs=nsL4Ge3oEV3G_gZ28FkDuud+Zxpg@mail.gmail.com>
[not found] ` <2092961.OBFZWjSADL@fomalhaut>
[not found] ` <45c84c01-74ca-3739-6482-2bbc94de0e9a@gmail.com>
[not found] ` <00af136c637f5231670c0fb6f7906d42@autistici.org>
[not found] ` <f454d3d7-3e70-6eb3-44d6-8213b6888a37@gmail.com>
2022-12-24 5:58 ` NightStrike
2022-12-24 6:27 ` i.nixman
2022-12-24 13:50 ` i.nixman
2022-12-24 15:42 ` i.nixman
2022-12-24 15:57 ` i.nixman
2022-12-24 21:22 ` i.nixman
2022-12-25 1:10 ` Jonathan Yong
2023-01-09 21:56 ` Eric Botcazou
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=7c519f0b-2a6d-e9bf-993a-2eff2cdad418@126.com \
--to=lh_mouse@126.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=rep.dot.nop@gmail.com \
/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).