Path: ...!news.nobody.at!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.arch
Subject: Re: Computer architects leaving Intel...
Date: Sat, 07 Sep 2024 21:17:02 -0700
Organization: A noiseless patient Spider
Lines: 9
Message-ID: <86r09ulqyp.fsf@linuxsc.com>
References: <vaqgtl$3526$1@dont-email.me> <memo.20240830090549.19028u@jgd.cix.co.uk> <2024Aug30.161204@mips.complang.tuwien.ac.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Date: Sun, 08 Sep 2024 06:17:03 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="f4e3787f228c748b74e6d718e0ca7324";
	logging-data="1912798"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/+o7bXn3N2xQFGu/0MSWR/lgGyJK8/bw8="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:eKBIcvHdbNzoEVxWpiAoXSRB+Dg=
	sha1:8MC6MUHeOIdS0eD6IWaZg5/jhYU=
Bytes: 1463

anton@mips.complang.tuwien.ac.at (Anton Ertl) writes:

> There was still no easy way to determine whether your software
> that calls memcpy() actually works as expected on all hardware,

There may not be a way to tell if memcpy()-calling code will work
on platforms one doesn't have, but there is a relatively simple
and portable way to tell if some memcpy() call crosses over into
the realm of undefined behavior.