Re: how to avoid a memset() optimization

"Lars Duening" <lars@bearnip.com> writes:


>> [Declaring the array volatile is the right way to do it. The reason
>> volatile exists is to tell the compiler not to do otherwise valid
>> optimizations. -John]
>
>Which is good news for the C/C++ crowd (at least those with compliant
>compilers), but what about compilers for other languages?
>
>[If they have something like volatile, use it. If not, you're on your
>own. -John]


Most popular languages these days support a C interface, so you may be
able to use that to call an external routine written in C, using volatile,
which can clear out the memory.


Version 1.1 of the MS .NET CLR also provides routines for volatile memory
access in the standard library, for use from languages that don't have
direct support for volatile.
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
The University of Melbourne | of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh> | -- the last words of T. S. Garp.

Return to the comp.compilers page.
Search the comp.compilers archives again.