This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

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: Optimiser and memory mapped I/O

From: Toralf Lund <toralf at procaptura dot com>
To: Peter Barada <pbarada at mail dot wm dot sps dot mot dot com>
Cc: crossgcc at sources dot redhat dot com
Date: Thu, 25 Sep 2003 19:13:07 +0200
Subject: Re: Optimiser and memory mapped I/O
References: <3F731D94.4000001@procaptura.com> <200309251703.h8PH32u08946@hyper.wm.sps.mot.com>

Peter Barada wrote:

which it would be if 0xfe8001 and 0xfe8003 were normal memory locations. The problem is, they aren't; they are I/O maps. Write to 0xfe8001 is used for register select, and 0xfe8003 gets the actual value of the register. Any ways around this (besides not optimising at all)?

Use 'volatile':

Yes, that helped.

I've never actually used "volatile" before, so perhaps it was about time to start...

Cheers,

Toralf

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

References:
- Optimiser and memory mapped I/O
  - From: Toralf Lund
- Re: Optimiser and memory mapped I/O
  - From: Peter Barada

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