Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!1.eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: rhel 7 and kforth Date: Thu, 16 Apr 2015 17:47:55 -0700 Organization: A noiseless patient Spider Lines: 19 Message-ID: <87y4lrwpfo.fsf@jester.gateway.pace.com> References: <6b95db78-ff4c-42aa-9680-7e4e588f61a4@googlegroups.com> <29c7eb53-229e-40a4-9bad-0d14e953ebc3@googlegroups.com> <87f18d43-a91e-4ae7-b98a-2cf4b7227c47@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="bda44be170c76b3ef6d23fecd204a8fa"; logging-data="8176"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/abxEzsLxp/J7jV4M0UW8d" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:KDj+org5Dl+vVRaHdYAVafXtGMQ= sha1:88kk3r9efPjOZVV62+AK+q7YynA= Xref: csiph.com comp.lang.forth:38244 foxaudioresearch@gmail.com writes: >> > > > *GlobalSp-- = *(GlobalSp+2); *GlobalSp-- = *(GlobalSp+2); /* 2dup */ > As one who does not spin in the GCC circles, how does one report such > a situation and is there an expectation of when it will be fixed? I think the old code was not valid C since there is no sequence point created by the assignment operator. See: http://c-faq.com/expr/seqpoints.html It may have happened to work for a while but it was not guaranteed by the C spec. > It makes me appreciate being able to reach inside and look under the > hood of a Forth compiler and actually understand it. It's not a matter of examining the compiler. The C language specification is full of hazards like that, possibly to allow added parallelization opportunities for the compiler.