public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Robin Farine <acnrf@dial.eunet.ch>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/3584
Date: Sat, 07 Jul 2001 06:16:00 -0000 [thread overview]
Message-ID: <20010707131601.20916.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR libstdc++/3584; it has been noted by GNATS.
From: Robin Farine <acnrf@dial.eunet.ch>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, robin.farine@terminus.org,
acnrf@dial.eunet.ch, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: libstdc++/3584
Date: 07 Jul 2001 15:13:04 +0200
This message improves the syntax and semantics of the description I have
provided when I registered the bug report.
Description: Routines such as atomic_add() that read a memory location, apply
operations to the value read, use the swp instruction to update the
memory location and swp again if the value read the 2nd time
doesn't equal the value initially read, introduce a race
condition. The attachment illustrates such a case.
Robin
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3584&database=gcc
next reply other threads:[~2001-07-07 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-07 6:16 Robin Farine [this message]
2002-10-03 9:06 libstdc++/3584 rearnsha
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=20010707131601.20916.qmail@sourceware.cygnus.com \
--to=acnrf@dial.eunet.ch \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).