The pointer to the buffer in the declaration of this function could be volatile. Then the compiler can't just get rid of the call since by definition something else could be referencing the memory.
> > On Sat, 23 Nov 2002 22:00:24 -0500 (EST), Rich Salz wrote: > > >As-if what? If the memory isn't zero, abort() is called. > > But the compiler could know that the memory is zero, inline the check, and > then optimize it out. > > >Every single byte of the area in question is checked. > >Please explain how it could be while preserving the semantics. > > The code does nothing, so under the as-if rule, it can be removed entirely. > > DS > > > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] > Jeffrey Altman * Volunteer Developer Kermit 95 2.1 GUI available now!!! The Kermit Project @ Columbia University SSH, Secure Telnet, Secure FTP, HTTP http://www.kermit-project.org/ Secured with MIT Kerberos, SRP, and [EMAIL PROTECTED] OpenSSL. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
