From: "Zhu, Lipeng" <lipeng.zhu@intel.com>
To: "H.J. Lu" <hjl.tools@gmail.com>,
"sgk@troutmask.apl.washington.edu"
<sgk@troutmask.apl.washington.edu>
Cc: Lipeng Zhu via Fortran <fortran@gcc.gnu.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"Li, Tianyou" <tianyou.li@intel.com>,
"Deng, Pan" <pan.deng@intel.com>
Subject: [PATCH] libgfortran: Replace mutex with rwlock
Date: Wed, 28 Dec 2022 10:00:38 +0000 [thread overview]
Message-ID: <PH7PR11MB605616965C1177841AE59A899FF29@PH7PR11MB6056.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAMe9rOoU3ooV5+UoB69WgE8NipeJSWHe52x=-H=a4cSSTaR_Xw@mail.gmail.com>
> libstdc++ implements shared mutex with pthread_rwlock, which can
> libstdc++ conflict
> with the pthread_rwlock usage in libgcc. Lipeng, please limit the pthread_rwlock usage in libgcc only when __cplusplus isn't defined.
>
>
> --
> H.J.
Thanks for suggestion, send a V2 patch.
--
Lipeng Zhu
next prev parent reply other threads:[~2022-12-28 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 0:27 Lipeng Zhu
2022-12-26 0:57 ` Steve Kargl
2022-12-27 16:33 ` H.J. Lu
2022-12-28 10:00 ` Zhu, Lipeng [this message]
2022-12-22 2:19 Lipeng Zhu
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=PH7PR11MB605616965C1177841AE59A899FF29@PH7PR11MB6056.namprd11.prod.outlook.com \
--to=lipeng.zhu@intel.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=pan.deng@intel.com \
--cc=sgk@troutmask.apl.washington.edu \
--cc=tianyou.li@intel.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).