Article View: comp.lang.c.moderated
Article #2296Re: use of the break statement
From: Marc Espie
Date: Fri, 15 Mar 1996 03:14
Date: Fri, 15 Mar 1996 03:14
16 lines
1242 bytes
1242 bytes
In article <4i97m5$8j0@solutions.solon.com>, J. Kanze <kanze@gabi-soft.fr> wrote: >The fact that the output is different could very well indicate a problem >in your code. Many compilers will give different outputs according to >the optimization level if your code invokes undefined behavior. (The >classical case here: your code contains order of evaluation >dependancies.) gcc is notorious for initalizing automatic local variables to 0 when not optimizing. -- [nosave]<http://www.eleves.ens.fr:8080/home/espie/index.html> microsoft network is EXPLICITLY forbidden to redistribute this message. `Moon purismu powa, make up.... Tsuki ni kawatte, oshiokiyo !' Marc Espie (Marc.Espie@ens.fr)
Technical Details
Message-ID:
<4ianao$h7f@solutions.solon.com>Path:
arc1-ca.pugleaf.net!solon.com!not-for-mailReferences:
<4gfcl7$2ls@solutions.solon.com> <4h81gh$aql@solutions.solon.com> <4h9ml2$gub@solutions.solon.com> <4i97m5$8j0@solutions.solon.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!solon.com!not-for-mail From: espie@clipper.ens.fr (Marc Espie) Newsgroups: comp.lang.c.moderated Subject: Re: use of the break statement Date: 14 Mar 1996 21:14:32 -0600 Organization: Ecole Normale Superieure, Paris Sender: clc@solutions.solon.com Approved: clc@solutions.solon.com Message-ID: <4ianao$h7f@solutions.solon.com> References: <4gfcl7$2ls@solutions.solon.com> <4h81gh$aql@solutions.solon.com> <4h9ml2$gub@solutions.solon.com> <4i97m5$8j0@solutions.solon.com> NNTP-Posting-Host: solutions.solon.com