From: Michael Matz <matz@suse.de>
To: Martin Uecker <ma.uecker@gmail.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: reordering of trapping operations and volatile
Date: Fri, 14 Jan 2022 14:15:33 +0000 (UTC) [thread overview]
Message-ID: <alpine.LSU.2.20.2201141328210.4251@wotan.suse.de> (raw)
In-Reply-To: <c0ef311f6eea75f27f0cb4733510e62f27ae920b.camel@gmail.com>
Hello,
On Thu, 13 Jan 2022, Martin Uecker wrote:
> > > > Handling all volatile accesses in the very same way would be
> > > > possible but quite some work I don't see much value in.
> > >
> > > I see some value.
> > >
> > > But an alternative could be to remove volatile
> > > from the observable behavior in the standard
> > > or make it implementation-defined whether it
> > > is observable or not.
> >
> > But you are actually arguing for making UB be observable
>
> No, I am arguing for UB not to have the power
> to go back in time and change previous defined
> observable behavior.
But right now that's equivalent to making it observable,
because we don't have any other terms than observable or
undefined. As aluded to later you would have to
introduce a new concept, something pseudo-observable,
which you then started doing. So, see below.
> > That's
> > much different from making volatile not be
> > observable anymore (which obviously would
> > be a bad idea), and is also much harder to
>
> I tend to agree that volatile should be
> considered observable. But volatile is
> a bit implementation-defined anyway, so this
> would be a compromise so that implementations
> do not have to make all the implied changes
> if we revise the meaning of UB.
Using volatile accesses for memory mapped IO is a much stronger use-case
than your wish of using volatile accesses to block moving of UB as a
debugging aid, and the former absolutely needs some guarantees, so I don't
think it would be a compromise at all. Mkaing volatile not be observable
would break the C language.
> > Well, what you _actually_ want is an implied
> > dependency between some UB and volatile accesses
> > (and _only_ those, not e.g. with other UB), and the
> > difficulty now is to define "some" and to create
> > the dependency without making that specific UB
> > to be properly observable.
>
> Yes, this is what I actually want.
>
> > I think to define this
> > all rigorously seems futile (you need a new
> > category between observable and UB), so it comes
> > down to compiler QoI on a case by case basis.
>
> We would simply change UB to mean "arbitrary
> behavior at the point of time the erraneous
> construct is encountered at run-time" and
> not "the complete program is invalid all
> together". I see no problem in specifying this
> (even in a formally precise way)
First you need to define "point in time", a concept which doesn't exist
yet in C. The obvious choice is of course observable behaviour in the
execution environment and its specified ordering from the abstract
machine, as clarified via sequence points. With that your "at the point
in time" becomes something like "after all side effects of previous
sequence point, but strictly before all side effects of next sequence
point".
But doing that would have very far reaching consequences, as already
stated in this thread. The above would basically make undefined behaviour
be reliably countable, and all implementations would need to produce the
same counts of UB. That in turn disables many code movement and
commonization transformations, e.g. this:
int a = ..., b = ...;
int x = a + b;
int y = a + b;
can't be transformed into "y = x = a + b" anymore, because the addition
_might_ overflow, and if it does you have two UBs originally but would
have one UB after. I know that you don't want to inhibit this or similar
transformations, but that would be the result of making UB countable,
which is the result of forcing UB to happen at specific points in time.
So, I continue to see problems in precisely specifying what you want, _but
not more_.
I think all models in which you order the happening of UB with respect to
existing side effects (per abstract machine, so it includes modification
of objects!) have this same problem, it always becomes a side effect
itself (one where you don't specify what actually happens, but a side
effect nontheless) and hence becomes observable.
Ciao,
Michael.
next prev parent reply other threads:[~2022-01-14 14:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 8:32 Martin Uecker
2022-01-08 12:41 ` Richard Biener
2022-01-08 13:50 ` Martin Uecker
2022-01-08 14:13 ` Marc Glisse
2022-01-08 14:41 ` Eric Botcazou
2022-01-08 15:27 ` Martin Uecker
2022-01-08 17:33 ` Eric Botcazou
2022-01-08 15:03 ` David Brown
2022-01-08 16:42 ` Martin Uecker
2022-01-08 18:35 ` Andrew Pinski
2022-01-08 21:07 ` Martin Uecker
2022-01-10 9:04 ` Richard Biener
2022-01-10 17:36 ` Martin Uecker
2022-01-11 7:11 ` Richard Biener
2022-01-11 8:17 ` Martin Uecker
2022-01-11 9:13 ` Richard Biener
2022-01-11 20:01 ` Martin Uecker
2022-01-13 16:45 ` Michael Matz
2022-01-13 19:17 ` Martin Uecker
2022-01-14 14:15 ` Michael Matz [this message]
2022-01-14 14:58 ` Paul Koning
2022-01-15 21:28 ` Martin Sebor
2022-01-15 21:38 ` Paul Koning
2022-01-16 12:37 ` Martin Uecker
2022-01-14 15:46 ` Martin Uecker
2022-01-14 19:54 ` Jonathan Wakely
2022-01-15 9:00 ` Martin Uecker
2022-01-15 16:33 ` Jonathan Wakely
2022-01-15 18:48 ` Martin Uecker
2022-01-17 14:10 ` Michael Matz
2022-01-18 8:31 ` Richard Biener
2022-01-21 16:21 ` Martin Uecker
2022-01-11 18:17 ` David Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LSU.2.20.2201141328210.4251@wotan.suse.de \
--to=matz@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=ma.uecker@gmail.com \
--cc=richard.guenther@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).