public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joe Buck <jbuck@Synopsys.COM>
To: moshier@mediaone.net
Cc: jbuck@Synopsys.COM, tim@wagner.Princeton.EDU, law@cygnus.com,
	tprince@cat.e-mail.com, bosch@gnat.com, burley@gnu.org,
	egcs@cygnus.com, hjstein@bfr.co.il
Subject: Re: /internet
Date: Wed, 16 Dec 1998 11:59:00 -0000	[thread overview]
Message-ID: <199812161958.LAA29146@atrus.synopsys.com> (raw)
In-Reply-To: <Pine.LNX.4.05.9812161437430.31241-100000@moshier.ne.mediaone.net>

> > Does IEEE require left-to-right evaluation of y = a * b * c * d;
> > when there are no parentheses present?
> 
> I think that IEEE does not actually say anything about it.  C9X, however,
> does contain some remarks such as the following, which might have come
> from NCEG.

>                int a, b;
>                /* ... */
>                a = a + 32760 + b + 5;
> 
>        the expression statement behaves exactly the same as
> 
>                a = (((a + 32760) + b) + 5);
>
>        due to the associativity and precedence of these  operators.
>        Thus,  the result of the sum (a + 32760) is next added to b,
>        and that result is then added to  5  which  results  in  the
>        value  assigned  to  a.   On  a  machine  in which overflows
>        produce an explicit trap and in which the  range  of  values
>        representable   by   an   int   is   [-32768,  +32767],  the
>        implementation cannot rewrite this expression as
> 
>                a = ((a + b) + 32765);

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

If this is the rule, then a*b*c*d can't be rearranged in C9X.  However,
it appears that it can be rearranged in Fortran (where the user must
use parentheses to force the order of evaluation) as well as in the
current ANSI/ISO C.

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

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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             ` Joe Buck [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
1998-12-16 12:34 /internet Geert Bosch
1998-12-16 13:02 ` /internet Harvey J. Stein
1998-12-16 16:25 ` /internet Jeffrey A Law
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=199812161958.LAA29146@atrus.synopsys.com \
    --to=jbuck@synopsys.com \
    --cc=bosch@gnat.com \
    --cc=burley@gnu.org \
    --cc=egcs@cygnus.com \
    --cc=hjstein@bfr.co.il \
    --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).