Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!gatech!amd!eager
From: eager@amd.UUCP (mike eager)
Newsgroups: comp.lang.c
Subject: Re: Use of #pragma
Message-ID: <3917@amd.UUCP>
Date: Thu, 23-Apr-87 03:06:02 EST
Article-I.D.: amd.3917
Posted: Thu Apr 23 03:06:02 1987
Date-Received: Sat, 25-Apr-87 00:46:09 EST
References: <386@sdd.uucp> <6966@brl-adm.ARPA>
Reply-To: eager@amd.UUCP (mike eager)
Organization: Eager Consulting
Lines: 13
Summary: #pragma optional

Daniel Corbett (dc@sdd.uucp) writes:
>
>    Why not utilize a #pragma NO_OPTIMIZE & a counter pragma #pragma OPTIMIZE
>around code that is to executed as is  Perhaps we can even create various
>classes of pragmas for different optimizations:  #pragma NO_OPTIMIZE LOOPS,
>#pragma NO_OPTIMIZE_STRENGTH, etc.

Section 3.8.6 of the ANSI standard states "Any pragma that is not recognized 
by the implementation is ignored."  I might add, that there is no need for
the implementation to tell you that it ignored your advice.

What this means, is that NO #pragma can be relied upon to control expression
evaluation.