Path: csiph.com!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Alexis <flexibeast@gmail.com>
Newsgroups: comp.lang.c
Subject: "The provenance memory model for C", by Jens Gustedt
Date: Wed, 02 Jul 2025 14:22:28 +1000
Organization: A noiseless patient Spider
Lines: 27
Message-ID: <87o6u343y3.fsf@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Wed, 02 Jul 2025 06:22:30 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="0ff5c1962e24889494e541aae95fa378"; logging-data="3495792"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX198pPieKmxj+SjV4I+l9NVXF3mq5MQCfY8="
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:zv7mwmlfEm/KyQ4CzoEN+v5BY5Q= sha1:VukHCBje31dQ6ZhQ1ky48kH40G8=
Xref: csiph.com comp.lang.c:393959


Thought some here might find this interesting:

"Our provenance-aware memory object model for C provides a precise
mathematical specification, in place of the ambiguity of these aspects
of the current C standard. It has also stimulated and informed
discussion of provenance in the broader C, C++, Rust, and compiler
communities.

"This work has finally resulted in the publication of an international
standard, Technical Specification ISO/IEC TS 6010 (edited by Henry
Kleynhans, Bloomberg, UK) ...

"In this article, I will try to explain what this is all about, namely
on how a provenance model for pointers interferes with alias analysis of
modern compilers. For those that are not fluent with the terminology or
the concept we have a short intro what pointer aliasing is all about, a
review of existing tools to help the compiler and inherent difficulties
and then the proposed model itself. At the end there is a brief takeaway
that explains how to generally avoid complications and loss of
optimization opportunities that could result from mis-guided aliasing
analysis."

-- https://gustedt.wordpress.com/2025/06/30/the-provenance-memory-model-for-c/


Alexis.