From: Dr Iain Maoileoin <iain@csp-partnership.co.uk>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] DEC Compilers (was: Re: SDB debugger
Date: Tue, 5 May 2020 19:53:59 +0100 [thread overview]
Message-ID: <3C1A26DC-2FC2-4EEA-A7FF-32FFD83E0007@csp-partnership.co.uk> (raw)
In-Reply-To: <CABH=_VRSyg_FXokkhXa0SPwg2o8wVTy2XtOm9+RRJwVm8ft=gw@mail.gmail.com>
> On 5 May 2020, at 18:36, Paul Winalski <paul.winalski@gmail.com> wrote:
>
> On 5/4/20, Win Treese <treese@acm.org> wrote:
>>
>> ….
>> This caused a little bit of consternation with some of the compiler teams at
>> first.
>
> I remember that very well. IIRC it was called fuzz testing, and
> ….
> compiler team has also used random testing technology.
>
>> [1] https://www.hpl.hp.com/hpjournal/dtj/vol10num1/vol10num1art9.pdf
>
> -Paul W.
Way back in the deep past - late 70s I think - The Computer Science Department at Strathclyde Uni in Scotland had a contract to develop a test suite generator for the C compiler on the ICL perq computer. I think the testing/development for that compiler was happening at Dalkeith in Scotland - but dont quote me.
Like the above we generated programs (e.g. mixing short, int, long signed and unsigned and doing all sort of ops on them). The expected output was computed by the same C program running on a BSD unix vax and something else. We had a few issues with the vax and the other system disagreeing on the arithmetic results, but generally we were confident the random C programs would reasonably test the system under test. We did not get to see the results of the tests, we developed the suite and handed it over to ICL.
Overall we were not impressed by the PERQ and on a trip to Rutherford Appleton Labs (RAL) one November there was a HUGE bonfire being prepared (for our Guy Falkes(sp) celebration). The bonfire was generally comprised of the PERQ cardboard packing cases. It just looked like they were planning to burn the PERQs themselves. We agreed with the sentiment.
next prev parent reply other threads:[~2020-05-05 20:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 20:48 [TUHS] " Paul Ruizendaal
2020-05-01 21:57 ` Clem Cole
2020-05-02 9:10 ` Paul Ruizendaal
2020-05-02 16:04 ` Clem Cole
2020-05-01 23:05 ` Jeremy C. Reed
2020-05-02 0:49 ` Noel Hunt
2020-05-02 1:22 ` Rob Pike
2020-05-02 3:49 ` Noel Hunt
2020-05-02 20:16 ` Paul Ruizendaal
2020-05-03 6:58 ` arnold
2020-05-03 16:13 ` Clem Cole
2020-05-03 16:53 ` Henry Bent
2020-05-03 17:06 ` Henry Bent
2020-05-03 17:13 ` Henry Bent
2020-05-03 20:26 ` Clem Cole
2020-05-05 0:22 ` [TUHS] DEC Compilers (was: " Win Treese
2020-05-05 17:36 ` Paul Winalski
2020-05-05 18:53 ` Dr Iain Maoileoin [this message]
2020-05-05 21:59 ` Dan Cross
2020-05-05 21:49 ` Henry Bent
2020-05-03 17:35 ` [TUHS] " Paul Winalski
2020-05-03 21:27 ` Paul Ruizendaal
2020-05-12 4:15 ` Dave Horsfall
2020-05-06 2:52 [TUHS] DEC Compilers (was: " Doug McIlroy
2020-05-06 15:53 Doug McIlroy
2020-05-06 20:21 ` Tim Rylance
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=3C1A26DC-2FC2-4EEA-A7FF-32FFD83E0007@csp-partnership.co.uk \
--to=iain@csp-partnership.co.uk \
--cc=paul.winalski@gmail.com \
--cc=tuhs@minnie.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).