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_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 32585 invoked from network); 26 Mar 2023 15:04:57 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 26 Mar 2023 15:04:57 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id D3B5A411EC; Mon, 27 Mar 2023 01:04:55 +1000 (AEST) Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) by minnie.tuhs.org (Postfix) with ESMTPS id EBAF740D1D for ; Mon, 27 Mar 2023 01:04:50 +1000 (AEST) Received: by mail-pj1-x1031.google.com with SMTP id p3-20020a17090a74c300b0023f69bc7a68so6137766pjl.4 for ; Sun, 26 Mar 2023 08:04:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679843090; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Fjpp70OdGoiMpx2s6057icq5heBk1IcBhV0ENxT6SZs=; b=qnEYsiSPhzqNDDMqbDz5dg9eVNncGOCesCGgFtG5ISgozHiAmr6AqmsRhZbG1MWTyc /0azUvVhja16rD2NY/waepfZ+mKYsHPpuF6Jmw7S4aCREILQOIYWecwK7EWlvDF9b+uM lLluQr41p6ZLGkPBsEUmkeiJCofRSPYspbfl+BsBnWbvSCndwNn6muAZdOVtQLAzC4Lb foMKT9/Bhg9XJBxmZpJ3DHIaHH4YOis2UtrC8ofhilYfgNLrvd4WCkRXc2Z7QeuaS4lz 1rbmZPeb//lRTjK13W4ZyJr9Y2BQJmLWZzelbWI5iQ9id8o66uw7gf8ZoFV5C4zolrQz 3r7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679843090; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Fjpp70OdGoiMpx2s6057icq5heBk1IcBhV0ENxT6SZs=; b=6wctuhOX3XyB8ERIDf+BzcV3NmxH5AWmbBPXKspJDDlYo2wpIGQ4SB/Gl+2sWAVSGo YEUP/ncF7+PLEZIyorPbOb4K7RvEBUVy/0HA93C2kjQkPwR007gGdrqkEkP4w/2ZcbrZ HzkZZ89nX7DenYLyRm2o4YW0VXc2qi785HZVuQKp1U6KnxqfpPrzryp5LvdEK18AdnJ8 LbCCRV3WTs+roZ1Px/WI5IvoVyCD+hG9ljKrlnTZk21y0VA5uegnsgI+cGSdCsRAUFn3 3E1cP5as8iEMMlXmbmF/2oK9BQVJYIZTrKAfQ3+GjoGUHOcxan2LUuZ/I95vOfm/zmGA cKJQ== X-Gm-Message-State: AAQBX9eN+nT1blWoUXYhG9Uwyz6gzycudluAmD214s4NbHHNPO3EkYwd qrN2qHjojU+Q9HT8NIppLd6zR1ZLyhZaSTLQhO4= X-Google-Smtp-Source: AKy350Yyw82lNexZ79R/t9J1mJlKQ/mfA9KfjTvzyAsQydTH/yWryB+5rVbaWqJf5yHLvU4/ur2i/Xh4/u3coPJxFFg= X-Received: by 2002:a17:902:ba94:b0:19e:f660:81ee with SMTP id k20-20020a170902ba9400b0019ef66081eemr2944827pls.2.1679843090340; Sun, 26 Mar 2023 08:04:50 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:6a10:ce9e:b0:3bc:b7f6:895e with HTTP; Sun, 26 Mar 2023 08:04:49 -0700 (PDT) In-Reply-To: References: From: Paul Winalski Date: Sun, 26 Mar 2023 11:04:49 -0400 Message-ID: To: KenUnix Content-Type: text/plain; charset="UTF-8" Message-ID-Hash: SYOMUFN6JD4ZV4RFBYVTLN7V3N4QKIKL X-Message-ID-Hash: SYOMUFN6JD4ZV4RFBYVTLN7V3N4QKIKL X-MailFrom: paul.winalski@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: COFF X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [COFF] Re: Fortran Question for Unix System-V r3 List-Id: Computer Old Farts Forum Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On 3/26/23, KenUnix wrote: > Fortran question for Unix System-5 r3. > > When executing fortran programs requiring input the screen will > show a blank screen. After entering input anyway the program completes > under Unix System V *r3*. > > When the same program is compiled under Unix System V *r1* it > works as expected. > > Sounds like on Unix System V *r3* the output buffer is not being flushed. > I tried re-compiling F77. No help. Re-compiling F77 doesn't help because the bug is in the Fortran run-time library (RTL), not in the compiler. The routine that implements the READ statement should be flushing the write buffer before doing the actual read. Clearly it isn't. Their test system probably didn't have very many (if any) tests for interactive behavior. That sort of thing is difficult to automate. -Paul W.