Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: "Rod Pemberton" Newsgroups: comp.lang.forth Subject: Re: Static Single Assignment form to Stack allocation Date: Mon, 09 Feb 2015 02:35:40 -0500 Organization: Aioe.org NNTP Server Lines: 17 Message-ID: References: <82c4c3dc-7692-4d03-a447-9bdd54ff9387@googlegroups.com> <2015Feb6.142225@mips.complang.tuwien.ac.at> <26b59aed-f1a6-4ccb-90ad-69c36b1abb89@googlegroups.com> <7c2c334d-9b99-4667-a43f-74c553676ab5@googlegroups.com> NNTP-Posting-Host: n4wpt9zq8xR26Ttf9mo2BA.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Opera Mail/12.16 (Linux) X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.forth:36407 On Sun, 08 Feb 2015 15:09:59 -0500, Alex McDonald wrote: > on 08/02/2015 18:21:18, hugj wrote: >> All of this assumes that the compiler is non-optimizing --- >> that it is just compiling the source-code words into >> threaded-code words one-to-one and on e-by-one --- this >> is 1970s technology. > > Can you explain how forward references are resolved in an > optimizing compiler? The same way they're resolved in a non-optimizing compiler. Did you want an actual answer or were you just trolling Hugh? ... Rod Pemberton