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] |
On Thu, Aug 21, 2003 at 10:57:31AM -0500, Bill Gatliff wrote:
I don't see why Linus (or anyone else, for that matter) would have a problem understanding how "volatile" works.
I have a vague feeling that there used to be border cases for which gcc happened to produced bad code.
Either way, a quick search brought me to this post which explains it quite clearly (I think):
http://www.geocrawler.com/archives/3/597/2001/7/0/6253709/
Essentially, his appraoach allows to control where writing back to memory is relevant and where it isn't, while volatile forces it all the time.
Oh, and Linus's approach ties you inextricably to gcc. Mine works for any ANSI-compliant compiler.
Yes. Linux is really only target at GCC. Oh, and this is the x-gcc mailing list! :)
-- Bill Gatliff In the dark on embedded GNU? Step into the light. bgat@billgatliff.com
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |