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: Emulating diab compiler behaviour memory-is-volatile

From: Eljay Love-Jensen <eljay at adobe dot com>
To: "lapo_pasqui at libero dot it" <lapo_pasqui at libero dot it>, gcc-help <gcc-help at gcc dot gnu dot org>
Date: Mon, 10 Nov 2003 06:43:37 -0600
Subject: Re: Emulating diab compiler behaviour memory-is-volatile

Hi Lapo,

Consider one or more of these switches:
-fvolatile-static       Consider all mem refs to static data to be volatile
-fvolatile-global       Consider all mem refs to global data to be volatile
-fvolatile              Consider all mem refs through pointers as volatile
-ffloat-store           Do not store floats in registers

The last one has the added benefit of being closer to IEEE 754 compliance, albeit at a performance penalty on some* platforms.

HTH,
--Eljay

* by "some" I mean "all the ones I work on".

References:
- Emulating diab compiler behaviour memory-is-volatile
  - From: lapo_pasqui\ at libero\ dot it

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