From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: "Zhu, Lipeng" <lipeng.zhu@intel.com>
Cc: tkoenig@netcologne.de, fortran@gcc.gnu.org,
gcc-patches@gcc.gnu.org, "Lu, Hongjiu" <hongjiu.lu@intel.com>,
"Li, Tianyou" <tianyou.li@intel.com>,
"Deng, Pan" <pan.deng@intel.com>,
"Guo, Wangyang" <wangyang.guo@intel.com>
Subject: Re: [PATCH v3] libgfortran: Replace mutex with rwlock
Date: Mon, 8 May 2023 12:04:45 +0200 [thread overview]
Message-ID: <20230508120445.12109a08@nbbrfq> (raw)
In-Reply-To: <f29e541f-3029-6f2e-3a1f-798f9503a511@intel.com>
On Mon, 8 May 2023 17:31:27 +0800
"Zhu, Lipeng" <lipeng.zhu@intel.com> wrote:
> > BTW, did you look at the RELEASE semantics, respectively the note that one day (and now is that very
> > day), we might improve on the release semantics? Can of course be incremental AFAIC
> >
> Not quite understand your question about looking at the RELEASE
> semantics. Can you be more specific?
libgfortran/io/io.h: could be further optimized by making this be an __ATOMIC_RELEASE,
But let's defer that to a follow-up improvement independently of the
rwlock.
thanks,
next prev parent reply other threads:[~2023-05-08 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 9:31 Zhu, Lipeng
2023-05-08 10:04 ` Bernhard Reutner-Fischer [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-20 13:13 Zhu, Lipeng
2023-04-24 19:45 ` Bernhard Reutner-Fischer
[not found] <20221230001607.2232962-1-lipeng.zhu () intel ! com>
2023-04-19 7:06 ` Lipeng Zhu
2023-04-19 12:51 ` Bernhard Reutner-Fischer
2023-04-19 14:50 ` Bernhard Reutner-Fischer
2023-04-19 21:49 ` Bernhard Reutner-Fischer
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=20230508120445.12109a08@nbbrfq \
--to=rep.dot.nop@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongjiu.lu@intel.com \
--cc=lipeng.zhu@intel.com \
--cc=pan.deng@intel.com \
--cc=tianyou.li@intel.com \
--cc=tkoenig@netcologne.de \
--cc=wangyang.guo@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).