This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: volatile qualifier hurts single-threaded optimized case

From: Paolo Carlini <pcarlini at suse dot de>
To: Richard Guenther <richard dot guenther at gmail dot com>
Cc: Benjamin Kosnik <bkoz at redhat dot com>, libstdc++ <libstdc++ at gcc dot gnu dot org>
Date: Wed, 30 Aug 2006 11:30:03 +0200
Subject: Re: volatile qualifier hurts single-threaded optimized case
References: <84fc9c000608130242y5b25f33ap2dabc1ec7d19cd31@mail.gmail.com> <20060830110320.5709b6f3.bkoz@redhat.com> <44F559A3.5030204@suse.de> <84fc9c000608300227p17e35d38u7ac51e97e533f35d@mail.gmail.com>

Richard Guenther wrote:

Luckily rope is stupid and does not use atomic ops at all, but uses a mutex and manual increment/decrement. So rope is not an issue (until it gets atomic ops).

Exactly ;) *If* we drop your patch to rope (I didn't want to ;) the issue becomes only one of documentation...

Paolo.

References:
- volatile qualifier hurts single-threaded optimized case
  - From: Richard Guenther
- Re: volatile qualifier hurts single-threaded optimized case
  - From: Benjamin Kosnik
- Re: volatile qualifier hurts single-threaded optimized case
  - From: Paolo Carlini
- Re: volatile qualifier hurts single-threaded optimized case
  - From: Richard Guenther

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]