public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Werner Tuchan" <tuwn@gmx.net>
To: rth@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/5198: 3.0.3 linux x m68k build fail: invalid opcodes in c++locale.cc
Date: Tue, 05 Feb 2002 05:26:00 -0000	[thread overview]
Message-ID: <20020205132603.27034.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/5198; it has been noted by GNATS.

From: "Werner Tuchan" <tuwn@gmx.net>
To: "Aaron J. Grier" <aaron@frye.com>
Cc: <gcc-gnats@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>,
	<gcc-bugs@gcc.gnu.org>,
	<aaron@frye.com>,
	<miod@openbsd.org>,
	<jj@openbsd.org>,
	<espie@openbsd.org>
Subject: Re: libstdc++/5198: 3.0.3 linux x m68k build fail: invalid opcodes in c++locale.cc
Date: Tue, 5 Feb 2002 14:24:57 +0100

 > if we are turning off interrupts for the whole operation, and nobody
 > else can get into __exchange_and_add without turning off interrupts,
 > then why bother with the TAS at all?
 >
 > there's got to be an elegant solution somewhere.  :)
 >
 
 TAS is only needed for multiprocessor spinlocks. A second processor could
 concurrently enter even with interrupts disabled. This is the only reason
 why TAS exists at all otherwise you could just use BSET. TAS is atomic even
 on MP machines. Yet it is pretty unlikely that you find any multiprocessor
 machines with these CPUs nowadays.
 
 -Werner
 
 
 


             reply	other threads:[~2002-02-05 13:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05  5:26 Werner Tuchan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-04 14:36 Aaron J. Grier
2002-02-04 11:06 Werner Tuchan
2002-01-23 17:41 rth
2002-01-08 13:56 Aaron J. Grier
2002-01-04 15:36 Aaron J. Grier
2002-01-04 14:46 Craig Rodrigues
2002-01-04 14:36 Aaron J. Grier
2002-01-04 14:26 Craig Rodrigues
2002-01-04 13:56 Don Lindsay
2002-01-04 12:56 Craig Rodrigues
2002-01-04 12:26 Don Lindsay
2002-01-03 20:46 Craig Rodrigues
2002-01-03 20:16 Don Lindsay
2002-01-03 16:12 rodrigc
2002-01-03 15:47 rodrigc
2001-12-26 16:56 Don Lindsay
2001-12-26 16:20 rodrigc
2001-12-26 14:36 lindsayd

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=20020205132603.27034.qmail@sources.redhat.com \
    --to=tuwn@gmx.net \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=rth@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).