Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Thomas Koenig <tkoenig@netcologne.de>
Newsgroups: comp.arch
Subject: Re: Computer architects leaving Intel...
Date: Mon, 2 Sep 2024 17:59:16 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 21
Message-ID: <vb4udk$2ugqg$1@dont-email.me>
References: <2024Aug30.161204@mips.complang.tuwien.ac.at>
 <memo.20240830164247.19028y@jgd.cix.co.uk> <vasruo$id3b$1@dont-email.me>
 <2024Aug30.195831@mips.complang.tuwien.ac.at> <vat5ap$jthk$2@dont-email.me>
 <vaunhb$vckc$1@dont-email.me> <vautmu$vr5r$1@dont-email.me>
 <2024Aug31.170347@mips.complang.tuwien.ac.at>
 <vavpnh$13tj0$2@dont-email.me> <vb2hir$1ju7q$1@dont-email.me>
 <8lcadjhnlcj5se1hrmo232viiccjk5alu4@4ax.com> <vb3k0m$1rth7$1@dont-email.me>
 <17d615c6a9e70e9fabe1721c55cfa176@www.novabbs.org>
Injection-Date: Mon, 02 Sep 2024 19:59:17 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="0345d965feb7de85f7a1793c751a4a5d";
	logging-data="3097424"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19VEANe1kjOlui0r8ifaoMPcPBMTB2ImiA="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:P/skGnSWOh150ziln9GK4d4XmH4=
Bytes: 2035

MitchAlsup1 <mitchalsup@aol.com> schrieb:
> On Mon, 2 Sep 2024 5:55:34 +0000, Thomas Koenig wrote:
>
>> George Neuner <gneuner2@comcast.net> schrieb:
>>
>>> I'm not going to argue about whether UB in code is wrong.  The
>>> question I have concerns what to do with something that explicitly is
>>> mentioned as UB in some standard N, but was not addressed in previous
>>> standards.
>>>
>>> Was it always UB?  Or should it be considered ID until it became UB?
>>
>> Can you give an exapmple?
>
> Memcopy() with overlapping pointers.

Does anybody have the first edition of K&R around to check what is
explicity stated there?  

If both were intended to have the same functionality, it would have
been strange to define both.