The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: KenUnix <ken.unix.guy@gmail.com>
Cc: UNIX TUHS Group <tuhs@tuhs.org>
Subject: [TUHS] Re: Fortran question for Unix System-5 r3
Date: Sun, 26 Mar 2023 11:10:57 -0400	[thread overview]
Message-ID: <CABH=_VRR2pNMYob7eEMeWc-mEBFaNv-25upbNrsL1MG96KY+Kg@mail.gmail.com> (raw)
In-Reply-To: <CAJXSPs92DGWxnfrUXfYF=3RP3TP4Og5rzr40OUTqZORq_Fofdw@mail.gmail.com>

[already answered in COFF, but since it is Unix-related I'll answer
here as well]

On 3/26/23, KenUnix <ken.unix.guy@gmail.com> 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.

The bug is almost certainly in the Fortran run-time library (RTL), not
in the compiler, so rebuilding the compiler won't help.

As a compiler engineer for many years, this regression bug got me
curious as to the software development processes in place for Unix
System V.  How was testing and release qualification done for f77 and
other utilities released with System V?  Was an automated test system
used?  Were reported and fixed bugs turned into regression tests?

Apropos this regression bug in particular, what testing of interactive
functionality was done, and how was it done?  Automating interactive
testing can be cussedly difficult.

-Paul W.

      reply	other threads:[~2023-03-26 15:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-26 14:00 [TUHS] " KenUnix
2023-03-26 15:10 ` Paul Winalski [this message]

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='CABH=_VRR2pNMYob7eEMeWc-mEBFaNv-25upbNrsL1MG96KY+Kg@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=ken.unix.guy@gmail.com \
    --cc=tuhs@tuhs.org \
    /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 NNTP newsgroup(s).