Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.sys.atari.st    |    Discussion about 16 bit Atari micros    |    15,439 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 15,008 of 15,439    |
|    Francois LE COAT to Michael Schwingen    |
|    Re: GNU/GCC optimizing    |
|    04 Oct 15 15:15:31    |
      From: lecoat@atari.org              Hi,              Michael Schwingen writes:       > Francois LE COAT wrote:       >> Well, the starting demo with a spinning hypercube is not played. The       >> GEM interface seems correct, but if I want to describe a curve, the       >> curve is not drawn. If I want to draw a surface, the surface is       >> not drawn. Nothing happens with the binary like it should. The       >> binary is simply not corresponding to sources. The program is broken.       >       > Im my experience with optimizing compilers, in most such cases the fault is       > not with the compiler, but instead the source code is broken, doing things       > that are not allowed by the C standard and relying on undefined behaviour.       >       > If it worked with the older compiler (that had a weaker optimizer) that does       > not mean anything for the correctness of the source code.       >       > Did you compile with all warning enabled, and look at the warnings? I can't       > believe old, misbehaving code would compile after a gcc3 -> gcc4 switch       > without producing at least some new warnings!              You'll agree that it's very peculiar ... How bizarre a warning will       generate an error when building C program's sources ? This is not       a warning, but should be alerted as an error, don't you think so ?       I never seen before in the C standard definition that a warning       should imperatively be taken into account, otherwise generating an       error. The warnings must often, used to generate good code, not errors.       Strong optimizations mean that warnings are now considered as errors ?              Please take into account that I practice C language since 1986,       first Kernighan and Ritchie, then ANSI C standard. Notice the       C standard must have evoluted because my C sources are now obsolete.              Thanks for your answer.              Best regards,              --        François LE COAT       Author of Eureka 2.12 (2D Graph Describer, 3D Modeller)       http://eureka.atari.org/              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca