From: Eljay Love-Jensen <eljay@adobe.com>
To: "lapo_pasqui@libero.it" <lapo_pasqui@libero.it>,
gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Emulating diab compiler behaviour memory-is-volatile
Date: Mon, 10 Nov 2003 12:42:00 -0000 [thread overview]
Message-ID: <5.2.1.1.0.20031110064125.014c1d58@iplan-mn.corp.adobe.com> (raw)
In-Reply-To: <HO4QW3$1C5B4D38E89C35634A0C1C22A8B43A24@libero.it>
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".
prev parent reply other threads:[~2003-11-10 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 9:40 lapo_pasqui
2003-11-10 12:42 ` Eljay Love-Jensen [this message]
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=5.2.1.1.0.20031110064125.014c1d58@iplan-mn.corp.adobe.com \
--to=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
--cc=lapo_pasqui@libero.it \
/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).