Path: ...!news.mixmin.net!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: Sat, 31 Aug 2024 11:26:58 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 18
Message-ID: <vauum2$10cpt$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>
Injection-Date: Sat, 31 Aug 2024 13:26:58 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="d78104b68bd6a6a358e9a21ee9fe1069";
	logging-data="1061693"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+OwLiokhPCKGU19wp3/FHICznUoMYVC7E="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:exPmDnVwcj6n78iI8GiUNSMxKOU=
Bytes: 1326

So, sorry for the too-quick examples earlier...

What about

int foo (int a)
{
  return a + 1;
}

or

int foo(int *a)
{
  return *a;
}

Both can exhibit undefined behavior, and for both it
is impossible for the compiler to tell at compile-time.