From: Jerry D <jvdelisle2@gmail.com>
To: fortran@gcc.gnu.org
Subject: Re: [PATCH] libgfortran: Bugfix if not define HAVE_ATOMIC_FETCH_ADD
Date: Wed, 3 Jan 2024 14:04:40 -0800 [thread overview]
Message-ID: <d75afba4-fa14-4d22-bdbd-ce2b2e8e7e14@gmail.com> (raw)
In-Reply-To: <d2d7e33b-7d0f-4ff3-bfe5-524c968fd2c0@codesourcery.com>
On 1/3/24 3:12 AM, Tobias Burnus wrote:
> On 22.12.23 03:36, Lipeng Zhu wrote:
>> This patch try to fix the bug when HAVE_ATOMIC_FETCH_ADD is
>> not defined in dec_waiting_unlocked function.
>>
>> 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>
>
> The change looks good to me + I assume it will work, but have not tested
> it myself.
>
> Downside is that it slightly breaks with the abstraction done with all
> the macros, but it seems to be the simplest solution.
>
> What is really missing - and should be included in the commit message
> (before the ChangeLog block) - is the following information:
>
> As io.h does not include async.h, the WRLOCK and RWUNLOCK macros are
> undefined.
>
---- snip ----
Would it make sense to include or merge async.h into io.h?
Jerry
next prev parent reply other threads:[~2024-01-03 22:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 2:36 Lipeng Zhu
2024-01-03 11:12 ` Tobias Burnus
2024-01-03 22:04 ` Jerry D [this message]
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
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=d75afba4-fa14-4d22-bdbd-ce2b2e8e7e14@gmail.com \
--to=jvdelisle2@gmail.com \
--cc=fortran@gcc.gnu.org \
/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).