This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC 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: Question on volatile functions and GCC

From: David Paterson <dnpaterson at gmail dot com>
To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
Cc: noloader at gmail dot com, gcc-help at gcc dot gnu dot org
Date: Tue, 5 Mar 2013 09:58:32 +0000
Subject: Re: Question on volatile functions and GCC
References: <CAH8yC8=iFF-74qkAoTyEVSWnTKaKcZAtGfj+eRHQj1WMa0A4zg@mail.gmail.com> <CAM1kHc2Xuwnpjg1pAL7jBRHhpsrSeqYAjyDVC6UWpXub1YLHeQ@mail.gmail.com> <CAH6eHdTpzzHjzi+n2=ESDP=eDm060x_Cs4MXpJ_WNHOjKKShzw@mail.gmail.com>

On 5 March 2013 09:40, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 5 March 2013 09:27, David Paterson wrote:
>>
>> In addition to Jonathan's answer on the use of "volatile", it's worth adding
>> that it's not only used for memory mapped hardware. There are many other
>> uses, such as inter-thread communication, or indeed the example you
>> show below.
>
> Only in broken code.

LOL - well, it depends on your definition of "broken"...

> volatile is not for multithreading, you need proper synchronization
> for interthread communication.

Not always.  For very simple, non-critical uses you can just use a
volatile flag-type variable.  Cheap and nasty, I agree, but useable.

Regards,

David P.

Follow-Ups:
- Re: Question on volatile functions and GCC
  - From: David Brown
- Re: Question on volatile functions and GCC
  - From: Ian Lance Taylor

References:
- Question on volatile functions and GCC
  - From: Jeffrey Walton
- Re: Question on volatile functions and GCC
  - From: David Paterson
- Re: Question on volatile functions and GCC
  - From: Jonathan Wakely

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