From ff0ed3e71cb828103cf21442231686f1b348479b Mon Sep 17 00:00:00 2001
From: Victor Stinner <victor.stinner@gmail.com>
Date: Thu, 10 Sep 2015 13:25:17 +0200
Subject: [PATCH] New try to fix test_time.test_AsSecondsDouble() on x86
 buildbots.

Use volatile keyword in _PyTime_AsSecondsDouble()
---
 Python/pytime.c | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/Python/pytime.c b/Python/pytime.c
index 9470636fdc7..c82d5985b47 100644
--- a/Python/pytime.c
+++ b/Python/pytime.c
@@ -332,16 +332,21 @@ _PyTime_FromMillisecondsObject(_PyTime_t *t, PyObject *obj, _PyTime_round_t roun
 double
 _PyTime_AsSecondsDouble(_PyTime_t t)
 {
+    /* volatile avoids optimization changing how numbers are rounded */
+    volatile double d;
+
     if (t % SEC_TO_NS == 0) {
         _PyTime_t secs;
         /* Divide using integers to avoid rounding issues on the integer part.
            1e-9 cannot be stored exactly in IEEE 64-bit. */
         secs = t / SEC_TO_NS;
-        return (double)secs;
+        d = (double)secs;
     }
     else {
-        return (double)t / 1e9;
+        d = (double)t;
+        d /= 1e9;
     }
+    return d;
 }
 
 PyObject *