[DTrace-devel] timestamp patch
eugene.loh at oracle.com
eugene.loh at oracle.com
Sat Jul 18 08:12:41 PDT 2020
In retrospect, this patch should probably wait until Kris has
finished putting back his compiler changes. Ah well. Take a
look if you like.
I am curious about one thing. With legacy DTrace,
BEGIN{trace(timestamp)}
BEGIN{trace(timestamp)}
would return two different values. Once Kris's compiler changes
are finished, will those two clauses be squashed to
BEGIN{trace(timestamp);
trace(timestamp)}
resulting in the same value being reported both times? Again,
I'm simply curious. Such a change in semantics is both subtle
and arguably even desirable.
More information about the DTrace-devel
mailing list