From 5f9dcd5364993f32e6841ffdfefce1cc87017b22 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Thu, 22 Nov 2018 12:24:38 +0200 Subject: Make backwards modification time check permanent, add another experiment --- build2/cc/compile-rule.cxx | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'build2/cc/compile-rule.cxx') diff --git a/build2/cc/compile-rule.cxx b/build2/cc/compile-rule.cxx index e361e9d..9326193 100644 --- a/build2/cc/compile-rule.cxx +++ b/build2/cc/compile-rule.cxx @@ -4249,7 +4249,8 @@ namespace build2 return *pr.first; } - // Make sure depdb is no older than any of our prerequisites. + // Make sure depdb is no older than any of our prerequisites (see md.mt + // logic description above for details). // touch (md.dd, false, verb_never); @@ -4668,11 +4669,14 @@ namespace build2 rm.cancel (); } + timestamp now (system_clock::now ()); + depdb::verify (timestamp_unknown, md.dd, tp, now); + // Should we go to the filesystem and get the new mtime? We know the // file has been modified, so instead just use the current clock time. // It has the advantage of having the subseconds precision. // - t.mtime (system_clock::now ()); + t.mtime (now); return target_state::changed; } -- cgit v1.1