public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Geert Bosch" <bosch@gnat.com>
To: "Joe Buck" <jbuck@synopsys.com>,
	"moshier@mediaone.net" <moshier@mediaone.net>
Cc: "burley@gnu.org" <burley@gnu.org>,
	"egcs@cygnus.com" <egcs@cygnus.com>,
	"hjstein@bfr.co.il" <hjstein@bfr.co.il>,
	"jbuck@synopsys.com" <jbuck@synopsys.com>,
	"law@cygnus.com" <law@cygnus.com>,
	"tim@wagner.princeton.edu" <tim@wagner.princeton.edu>,
	"tprince@cat.e-mail.com" <tprince@cat.e-mail.com>
Subject: Re: /internet
Date: Wed, 16 Dec 1998 12:34:00 -0000	[thread overview]
Message-ID: <9812162034.AA17456@nile.gnat.com> (raw)

On Wed, 16 Dec 98 11:58:08 PST, Joe Buck wrote:

  Amazing.  These guys are trying to turn C into Ada.

If that's true, they are doing it all wrong! :-)
In Ada95 rules have be precisely chosen such to allow 
useful optimizations like these. See my previous message 
where I explain how checks (and as a result operations) 
may be removed. 

Another useful difference is that in Ada evaluations of
functions in "pure" packages are guaranteed to be free of 
side-effects and may reuse results of earlier invocations 
with the same parameters. GCC takes full advantage of this 
by moving them out of loops etc. Of course all elementary 
fpt functions (including complex ones) are defined in pure 
packages and this leads to nice optimizations without sacrifying 
one bit of accuracy.

Those guys should copy these features instead of ones they make up!

Regards,
   Geert


             reply	other threads:[~1998-12-16 12:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-16 12:34 Geert Bosch [this message]
1998-12-16 13:02 ` /internet Harvey J. Stein
1998-12-16 16:25 ` /internet Jeffrey A Law
  -- strict thread matches above, loose matches on Subject: below --
1998-12-15 15:06 /internet tprince
1998-12-15 19:12 ` /internet Stephen L Moshier
1998-12-15 19:21   ` /internet Joe Buck
1998-12-15 19:37     ` /internet Jeffrey A Law
1998-12-16  7:58       ` /internet Tim Hollebeek
1998-12-16  8:41         ` /internet Joe Buck
1998-12-16 11:45           ` /internet Stephen L Moshier
1998-12-16 11:59             ` /internet Joe Buck
1998-12-16 13:19               ` /internet Chip Salzenberg
1998-12-16 16:20                 ` /internet Jeffrey A Law
1998-12-16 17:42                   ` /internet Joern Rennecke
1998-12-17  9:46                     ` /internet Horst von Brand
1998-12-16 16:37               ` /internet Jeffrey A Law
1998-12-16 16:56                 ` /internet Per Bothner
1998-12-17 20:20                   ` /internet Jeffrey A Law
1998-12-16 17:52                 ` /internet Joern Rennecke
1998-12-17  4:43                 ` /internet Sylvain Pion
1998-12-17 10:26               ` /internet Craig Burley
1998-12-15 23:08     ` /internet Matthias Urlichs
1998-12-16  9:33       ` /internet Craig Burley
1998-12-16  5:44     ` /internet Stephen L Moshier
1998-12-16  9:37   ` /internet Craig Burley
1998-12-04 17:41 /internet tprince

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9812162034.AA17456@nile.gnat.com \
    --to=bosch@gnat.com \
    --cc=burley@gnu.org \
    --cc=egcs@cygnus.com \
    --cc=hjstein@bfr.co.il \
    --cc=jbuck@synopsys.com \
    --cc=law@cygnus.com \
    --cc=moshier@mediaone.net \
    --cc=tim@wagner.princeton.edu \
    --cc=tprince@cat.e-mail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).