Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.arch
Subject: Re: Origins Of Interrupts
Date: Fri, 3 Jan 2025 03:49:28 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 20
Message-ID: <vl7mo8$3od64$1@dont-email.me>
References: <vl7j8d$3k2o4$2@dont-email.me> <vl7lbc$1s3m$1@gal.iecc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 03 Jan 2025 04:49:28 +0100 (CET)
Injection-Info: dont-email.me; posting-host="c1dc6161c0b733ffa77e30ced8836776";
	logging-data="3945668"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19BtdMn0jlmLgKXXhgZQfXG"
User-Agent: Pan/0.161 (Chasiv Yar; )
Cancel-Lock: sha1:vUkUdYaidlMjhdJEguBbKBtdUlg=
Bytes: 1778

On Fri, 3 Jan 2025 03:25:32 -0000 (UTC), John Levine wrote:

> According to Lawrence D'Oliveiro  <ldo@nz.invalid>:
>>
>> There is an Asianometry video which says that the first computer to
>> have interrupts was the Univac 1103.
>>
>> Does this sound right? What’s the earliest architecture anybody knows
>> of that had support for interrupts?
> 
> This informative web page repeats that claim but then says he thinks the
> Univac I had an overflow trap several years earlier:
> 
> https://people.computing.clemson.edu/~mark/interrupts.html

OK, but an overflow trap is a synchronous notification from the CPU to do 
with the current instruction.

To be clear, I was specifically thinking of asynchronous notifications to 
do with external conditions (typically I/O).