From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 20014 invoked from network); 26 Nov 2021 21:24:21 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 26 Nov 2021 21:24:21 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 283839CE6A; Sat, 27 Nov 2021 07:24:19 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id A4E1E9CE5D; Sat, 27 Nov 2021 07:22:29 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=ccil-org.20210112.gappssmtp.com header.i=@ccil-org.20210112.gappssmtp.com header.b="yZuNSzg5"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 8D77F9CE5D; Sat, 27 Nov 2021 07:22:27 +1000 (AEST) Received: from mail-qt1-f177.google.com (mail-qt1-f177.google.com [209.85.160.177]) by minnie.tuhs.org (Postfix) with ESMTPS id B0F9094942 for ; Sat, 27 Nov 2021 07:22:26 +1000 (AEST) Received: by mail-qt1-f177.google.com with SMTP id t34so10111161qtc.7 for ; Fri, 26 Nov 2021 13:22:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccil-org.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=F+YpVBS/hE/URHlxfHq2UetKvFsdi7Glv5mM3pCSbi8=; b=yZuNSzg5SdM/UUfBhLA0z9GMboWlXeoxYpapDU/BsiA8LWRbaJOLPaM0wlCe775H1p osbzyiAPqAkqGXzZeIlr4G48VT79KNDY3lS17mkERh/FXMLNx7JcI94/Lv047YBTh/HD WGIoKZy5hpI7zvT0WH9I8hR0SsP8mhpIMteaWtvddSMVIyPLyydE5+VdW/IBfEWg+ef3 s9BIxVUXY+Avc4JWdx1oaiG2sVC/i0REvpUyWXIsiFmKyP7nR5t5v2zEqO3aJWU9l5o5 yoH4AbXstCndMnwd1fS7W9syTKTG/eBOWi+1Aq8bKXTC3DIpcfkM7VI+o2RBv6+1lJ2D c80A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=F+YpVBS/hE/URHlxfHq2UetKvFsdi7Glv5mM3pCSbi8=; b=hd/V3HgesvAf19X1DbIA6iF1BBkWxw8LYPG6FYX+HNIRe7UCOp8Nc3BI4oD42fjmxN DXSsoYBe5OyjSlX2K5Q3H7nNrxlNkdGLGOTFvaYGkSyFS6srTgwz+WQD+ByMYv4lhXD9 s6HT4QhsA1igQWVdglA/f592jfdB+/FKOdkWGkx31Z0F/bOLbH0B7DM3Vj1NoozZwdS7 Yfz5pJpIUVow5UjZgHTr0Y1AsTNG+UNwrI9ivbT9R9CEN93ARubgOYb2bvK3CxGNU0uP isxl8I160RWO74oRK/7tbUr5dwuviyQtfzS0/Y1rlLP4gcRBxSuBTPV6YynXViA6fNx6 FslQ== X-Gm-Message-State: AOAM533gkYOBthzBAbLFUmGoEHAF3fk/dB8wqbBeu2Kaxd/6bLAbY8h/ LJF6mZEg4zuXqphDpIQi1u24erxecj0MeK2VqEgB+Q== X-Google-Smtp-Source: ABdhPJyV+Fv9JhGPaSzE9dlKikX06vm98Y7rFuwuG5WRCMxPgQuEr5z21soVZMq+Hy41nZextG4kibhxy78B8S3L8Cg= X-Received: by 2002:a05:622a:386:: with SMTP id j6mr18331625qtx.598.1637961745599; Fri, 26 Nov 2021 13:22:25 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: John Cowan Date: Fri, 26 Nov 2021 16:22:15 -0500 Message-ID: To: Tom Ivar Helbekkmo Content-Type: multipart/alternative; boundary="00000000000000a72805d1b7b021" Subject: Re: [TUHS] PL/I stuff - was: Book Recommendation X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: TUHS main list , Douglas McIlroy Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --00000000000000a72805d1b7b021 Content-Type: text/plain; charset="UTF-8" On Fri, Nov 26, 2021 at 3:32 PM Tom Ivar Helbekkmo via TUHS < tuhs@minnie.tuhs.org> wrote: Is there any relationship, other than pure coincidence, between this > naming scheme and DEC's F, G, and H floating point number formats? > I don't think so. The System/360 letters referred specifically to the amount of memory available, so a D compiler would run on a D machine with 256K, and E/F/G were 512K/1M/2M. The DEC floats were an extension of Fortran's exponent letters: D=double, E=generic, F=single. G is a variant of F with a different mantissa/exponent balance, and H is double double. S and T floats came later and were bit-for-bit compatible with IEEE binary32 and binary64 formats. Lisp went a different way: to D, E, F they added S for small floats and L for large floats. --00000000000000a72805d1b7b021 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Nov 26, 2= 021 at 3:32 PM Tom Ivar Helbekkmo via TUHS <tuhs@minnie.tuhs.org> wrote:

Is there any relationship, other than pure coincidence, between this
naming scheme and DEC's F, G, and H floating point number formats?
<= /blockquote>

I don't think so.= =C2=A0 The System/360 letters referred specifically to the amount of memory= available, so a D compiler would run on a D machine with 256K, and E/F/G w= ere 512K/1M/2M.

The DEC floats were an extension of Fortran's=C2=A0exponent let= ters:=C2=A0 D=3Ddouble, E=3Dgeneric, F=3Dsingle.=C2=A0 G is a variant of F = with a different mantissa/exponent balance, and H is double double.=C2=A0 = =C2=A0S and T floats came later and were bit-for-bit compatible with IEEE b= inary32 and binary64 formats.=C2=A0 Lisp went a different way: to D, E, F t= hey added S for small floats and L for large floats.
--00000000000000a72805d1b7b021--