Jens Maurer <Jens.Maurer_at_[hidden]> wrote:

[...]

| > What does "behavior of unrelated code" even mean once we've invoked
| > undefined behavior?
|
| Well, I thought the goal of SG12 was to discuss whether the current
| definition of "undefined behavior" should be retained for some (which?)
| cases, or whether something could be done to restrain the set of valid
| executions. For example, we already have the concept of "unspecified
| behavior", e.g. the sequencing of evaluation of function arguments is
| unspecified. This means the implementation is restricted to choose
| among a set of possible behaviors, and not exhibit arbitrary behavior.

That is correct.

The problems we are facing are real, and unfortunately, not vanishing.

-- Gaby