From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,99a6311c4195e21b X-Google-Attributes: gid103376,public X-Google-Thread: 1094ba,99a6311c4195e21b X-Google-Attributes: gid1094ba,public From: Robert A Duff Subject: Re: Matrix Multiplication Date: 1999/12/16 Message-ID: #1/1 X-Deja-AN: 561558951 Sender: bobduff@world.std.com (Robert A Duff) References: <385699B5.59C14D03@lmco.com> <838koc$b6d$1@nnrp1.deja.com> <3857E220.26AE90BB@lanl.gov> <8390te$ksp$1@nnrp1.deja.com> <385811C8.1E138A9E@lanl.gov> Organization: The World Public Access UNIX, Brookline, MA Newsgroups: comp.lang.ada,comp.lang.fortran Date: 1999-12-16T00:00:00+00:00 List-Id: "William B. Clodius" writes: >...If I remember correctly, Ada requires > either copy-in/copy-out or call by reference semantics by the compiler > (without specifying the choice made) in most contexts, ... I believe RM-6.2(12) allows substantially more freedom to the compiler than that. But you are correct that it's not *quite* as much freedom as Fortran allows. Pretty close, though, I think. >...while Fortran > requires that code allow either copy-in/copy-out or call by reference > implementation, but does not require that the actual implementation be > consistent with either semantics, i.e. at arbitrary points in the > procedure arguments can be copied-in/copied-out without synchronizing > with other copy-ins/copy-outs. ... Anyway, there's an important non-technical issue: How much money are people willing to expend on making optimizing compilers. - Bob