From 6a40900dcd085cd3166a9d89eebf3538111c5416 Mon Sep 17 00:00:00 2001 From: Richard Brooksby Date: Sun, 2 Sep 2012 16:48:23 +0100 Subject: [PATCH] Updating procedure for testing check macros to fit new variety scheme. Copied from Perforce Change: 179176 ServerID: perforce.ravenbrook.com --- mps/code/check.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/mps/code/check.h b/mps/code/check.h index 3ba0fff138b..d338fb0fa5a 100644 --- a/mps/code/check.h +++ b/mps/code/check.h @@ -23,9 +23,9 @@ * without realising it. This has happened before. Eyeball the preprocessor * output for each variety. For example: * - * cc -E -DCONFIG_PROD_MPS -DCONFIG_VAR_WE trace.c - * cc -E -DCONFIG_PROD_MPS -DCONFIG_VAR_HE trace.c - * cc -E -DCONFIG_PROD_MPS -DCONFIG_VAR_CI trace.c + * cc -E -DCONFIG_VAR_WE trace.c + * cc -E -DCONFIG_VAR_HOT trace.c + * cc -E -DCONFIG_VAR_COOL trace.c * * Then look at TraceCheck to make sure checking is right, TraceAddWhite * for general assertions, and TraceFix for the critical path assertions.