From d26f14f316cdf6ee2b6bc35eaa78cfa827580ec2 Mon Sep 17 00:00:00 2001
From: Richard Kistruck
Date: Tue, 11 Nov 2008 10:39:53 +0000
Subject: Mps br/timing: do not set postedclock for finalization msgs.

Copied from Perforce
 Change: 166690
 ServerID: perforce.ravenbrook.com

---
 mps/code/message.c | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

(limited to 'mps/code')

diff --git a/mps/code/message.c b/mps/code/message.c
index 0c6c3beaae4..2e63c80f025 100644
--- a/mps/code/message.c
+++ b/mps/code/message.c
@@ -122,9 +122,11 @@ void MessagePost(Arena arena, Message message)
   /* <design/message/#fun.post.singleton> */
   AVER(!MessageOnQueue(message));
   if(MessageTypeEnabled(arena, message->type)) {
-    /* @@@@ for finalization messages, this may be critical path; */
-    /* so is it still ok to call mps_clock() here? */
-    message->postedClock = mps_clock();
+    /* Setting clock involves mpslib call, so only do it for rare */
+    /* messages.  Currently: all messages except finalization. */
+    if(message->type != MessageTypeFINALIZATION) {
+      message->postedClock = mps_clock();
+    }
     RingAppend(&arena->messageRing, &message->queueRing);
   } else {
     /* discard message immediately if client hasn't enabled that type */
-- 
cgit v1.2.1