Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: VMS C: floating point precision
Message-ID: <6698@ucbvax.ARPA>
Date: Thu, 2-May-85 12:31:16 EDT
Article-I.D.: ucbvax.6698
Posted: Thu May  2 12:31:16 1985
Date-Received: Fri, 3-May-85 04:49:41 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 16

From: Jerry Wolf <WOLF@BBNG>

I understand that it's usual for C compilers in general (and VMS C
in particular) to convert all operands for floating point expressions
to double precision, even if there are no double-precision
operands on either side of the assignment; that is, any floating
point computation is converted to double precision, and then back
to single precision if necessary.

Is there any way to prevent this?  If I'm happy with single
precision (32-bit) floating point operands and operations,
why can't I just have it compile "ordinary" floating point
operations without all that extra work (and inefficiency)?
Will version 2.0 of C "fix" this?
Cheers,
  Jerry