This is the mail archive of the crossgcc@sourceware.cygnus.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more infromation.

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

Re: gcc volatile behaviour

To: zoltan at bendor dot com dot au
Subject: Re: gcc volatile behaviour
From: Ian Lance Taylor <ian at zembu dot com>
Date: 10 Oct 1999 16:40:23 -0400
CC: crossgcc at sourceware dot cygnus dot com
References: <939446722.24847.ezmlm@sourceware.cygnus.com><14335.14224.304921.369360@tade.bendor.com.au><19991009140428.21486.qmail@daffy.airs.com> <14335.59221.383822.782962@tade.bendor.com.au>

   From: Zoltan Kocsi <zoltan@bendor.com.au>
   Date: Sun, 10 Oct 1999 15:11:38 +1000 (EST)

   So, in the light of the above, would it be possible that in the next
   release of gcc/egcs there could be a switch to change this re-fetching
   behaviour, i.e. with the switch applied gcc/egcs would treat the 
   value of an assignment expression being the value that is *written* to 
   the left hand site (regardless of that being volatile or not) ?

Thanks for the research.

The approach most likely to succeed would be for you to implement the
change to gcc, and submit the patch to the gcc maintainers.  See
    http://sourceware.cygnus.com/gcc

Ian

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

References:
- gcc volatile behaviour
  - From: Zoltan Kocsi
- Re: gcc volatile behaviour
  - From: Ian Lance Taylor
- Re: gcc volatile behaviour
  - From: Zoltan Kocsi

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