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/link-rule.cxx | 25 ++----------------------- 1 file changed, 2 insertions(+), 23 deletions(-) (limited to 'build2/cc/link-rule.cxx') diff --git a/build2/cc/link-rule.cxx b/build2/cc/link-rule.cxx index 2581d6f..47c058d 100644 --- a/build2/cc/link-rule.cxx +++ b/build2/cc/link-rule.cxx @@ -2071,12 +2071,7 @@ namespace build2 if (dd.writing () || dd.mtime > mt) scratch = update = true; -#define BUILD2_MTIME_CHECK -#ifdef BUILD2_MTIME_CHECK - timestamp dd_tt (system_clock::now ()); -#endif - - timestamp dd_cl (dd.close ()); + dd.close (); // If nothing changed, then we are done. // @@ -2559,23 +2554,7 @@ namespace build2 } rm.cancel (); - -#ifdef BUILD2_MTIME_CHECK - { - timestamp tp_mt (file_mtime (tp)); - timestamp dd_mt (file_mtime (dd.path)); - timestamp tp_tt (system_clock::now ()); - - if (dd_mt > tp_mt) - fail << "backwards modification times:\n" - << dd_tt << " window start\n" - << dd_cl << " write mtime\n" - << dd.mtime << " close mtime\n" - << dd_mt << " " << dd.path.string () << '\n' - << tp_mt << " " << tp.string () << '\n' - << tp_tt << " window end"; - } -#endif + dd.verify (tp); // 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. -- cgit v1.1