From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: THE -O2 PROBLEM - PART II
Date: Sat, 15 Apr 2000 10:39:22 +0200
Organization: NetVision Israel	
Lines: 10
Message-ID: <38F82ABA.FEBEB2B0@is.elta.co.il>
References: <38F20E7A DOT 3330E9A4 AT mtu-net DOT ru> <38F6C64E DOT C7753C6C AT mtu-net DOT ru> <8d7l3g$j3i$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <38F76B94 DOT 5E968BA7 AT mtu-net DOT ru> <38F7A6FE DOT ED9B3E59 AT mtu-net DOT ru>
NNTP-Posting-Host: ras1-p73.rvt.netvision.net.il
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: news.netvision.net.il 955784313 26222 62.0.172.75 (15 Apr 2000 07:38:33 GMT)
X-Complaints-To: abuse AT netvision DOT net DOT il
NNTP-Posting-Date: 15 Apr 2000 07:38:33 GMT
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en,ru,hebrew
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

"Alexei A. Frounze" wrote:
> 
> But with optimizations enabled, I simply get faulty code, since compiler
> eliminates checking of the array. How to prevent this from optimizations?

If the compiler eliminates the entire inline asm block, one way to prevent it
is with "__asm__ __volatile__" instead of just "__asm__" or "asm".

If that's not the problem, I suggest to post the offending code fragment and
its surroundings.