From: Jakub Jelinek <jakub@redhat.com>
To: Lipeng Zhu <lipeng.zhu@intel.com>
Cc: tobias@codesourcery.com, Richard.Earnshaw@arm.com,
fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org,
hongjiu.lu@intel.com, pan.deng@intel.com, rep.dot.nop@gmail.com,
thomas@codesourcery.com, tianyou.li@intel.com,
tkoenig@netcologne.de, wangyang.guo@intel.com
Subject: Re: [PATCH v2] libgfortran: Bugfix if not define HAVE_ATOMIC_FETCH_ADD
Date: Thu, 11 Jan 2024 13:38:49 +0100 [thread overview]
Message-ID: <ZZ/hWW3YyITdq37F@tucnak> (raw)
In-Reply-To: <20240105014325.1490280-1-lipeng.zhu@intel.com>
On Thu, Jan 04, 2024 at 08:43:26PM -0500, Lipeng Zhu wrote:
> This patch try to fix the bug when HAVE_ATOMIC_FETCH_ADD is
> not defined in dec_waiting_unlocked function. As io.h does
> not include async.h, the WRLOCK and RWUNLOCK macros are
> undefined.
>
> libgfortran/ChangeLog:
>
> * io/io.h (dec_waiting_unlocked): Use
> __gthread_rwlock_wrlock/__gthread_rwlock_unlock or
> __gthread_mutex_lock/__gthread_mutex_unlock functions
> to replace WRLOCK and RWUNLOCK macros.
>
> Signed-off-by: Lipeng Zhu <lipeng.zhu@intel.com>
LGTM.
Jakub
prev parent reply other threads:[~2024-01-11 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 2:36 [PATCH] " Lipeng Zhu
2024-01-03 11:12 ` Tobias Burnus
2024-01-03 22:04 ` Jerry D
2024-01-04 2:18 ` Lipeng Zhu
2024-01-05 1:43 ` [PATCH v2] " Lipeng Zhu
2024-01-10 11:52 ` Richard Earnshaw
2024-01-11 3:05 ` Lipeng Zhu
2024-01-11 12:38 ` Jakub Jelinek [this message]
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=ZZ/hWW3YyITdq37F@tucnak \
--to=jakub@redhat.com \
--cc=Richard.Earnshaw@arm.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=rep.dot.nop@gmail.com \
--cc=thomas@codesourcery.com \
--cc=tianyou.li@intel.com \
--cc=tkoenig@netcologne.de \
--cc=tobias@codesourcery.com \
--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).