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,010 of 15,439    |
|    Francois LE COAT to Michael Schwingen    |
|    Re: GNU/GCC optimizing    |
|    04 Oct 15 22:30:21    |
      From: lecoat@atari.org              Hi,              Michael Schwingen writes:       > Francois LE COAT wrote:       >> 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 ?       >       > No. The C standard gives compiler writers considerable room in which way       > certain details may be implemented. If your source code uses constructs with       > undefined results, the results will be - well, undefined, and may change       > with compiler versions.       >       >> 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.       >       > It has - K&R left many things undefined which were better specified in ANSI       > C, however, even K&R had language details which caused undefined behaviour       > by definition, and which may now cause unexpected results due to improving       > compiler optimizations that uncover faults that were always there.       >       > As a start, have a look at       > http://blog.regehr.org/archives/213       > http://blog.llvm.org/2011/05/what-every-c-programmer-should-know.html              Well, the same recipe should at least give the same meal. If somebody       cooks a pizza, he is not supposed to eat a tomato ketchup. Except if       he is an extremely bad cooker. The recipes are the C language sources,       and the cooker is the C language compiler.              What should I think about GNU/GCC 4 compared to GNU/GCC 2 and 3,       PURE C 1.1 and other compilers, building my C program Eureka 2.12,       when the produced binary is such a messy meal ?              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