diff options
| author | Michael Widenius <monty@askmonty.org> | 2012-04-02 13:33:16 +0300 |
|---|---|---|
| committer | Michael Widenius <monty@askmonty.org> | 2012-04-02 13:33:16 +0300 |
| commit | d513153f77702dec4a20801a0078d57370b8fef6 (patch) | |
| tree | 4bbb4f2af59b22f4a8108238925f5c5e4b0926a4 /mysys/my_getsystime.c | |
| parent | 635598f19c3f9f8c2b03f417bff584e023a09f34 (diff) | |
| parent | ca28d5fcf82686f60b0e439e60fbbce5387d8ccd (diff) | |
| download | mariadb-git-d513153f77702dec4a20801a0078d57370b8fef6.tar.gz | |
Merge of compatibility fixes
Fixed failing tests in sys_vars as we have now stricter checking of setting of variables.
mysql-test/suite/sys_vars/r/innodb_adaptive_flushing_basic.result:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/r/innodb_adaptive_hash_index_basic.result:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/r/innodb_large_prefix_basic.result:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/r/innodb_random_read_ahead_basic.result:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/r/innodb_stats_on_metadata_basic.result:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/r/innodb_strict_mode_basic.result:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/r/innodb_support_xa_basic.result:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/r/innodb_table_locks_basic.result:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/r/rpl_semi_sync_master_enabled_basic.result:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/r/rpl_semi_sync_slave_enabled_basic.result:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/t/innodb_adaptive_flushing_basic.test:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/t/innodb_adaptive_hash_index_basic.test:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/t/innodb_large_prefix_basic.test:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/t/innodb_random_read_ahead_basic.test:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/t/innodb_stats_on_metadata_basic.test:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/t/innodb_strict_mode_basic.test:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/t/innodb_support_xa_basic.test:
One can now only assign 0 or 1 to boolean variables
mysql-test/suite/sys_vars/t/innodb_table_locks_basic.test:
One can now only assign 0 or 1 to boolean variables
mysys/my_getsystime.c:
Merge + fixed bug that __NR_clock_gettime didn't work in 5.5
Diffstat (limited to 'mysys/my_getsystime.c')
| -rw-r--r-- | mysys/my_getsystime.c | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/mysys/my_getsystime.c b/mysys/my_getsystime.c index f1caea6d21a..2a23a699f69 100644 --- a/mysys/my_getsystime.c +++ b/mysys/my_getsystime.c @@ -119,7 +119,6 @@ void my_time_init() ulonglong my_getcputime() { #ifdef CLOCK_THREAD_CPUTIME_ID -#ifdef HAVE_CLOCK_GETTIME struct timespec tp; if (clock_gettime(CLOCK_THREAD_CPUTIME_ID, &tp)) return 0; @@ -129,8 +128,6 @@ ulonglong my_getcputime() if (syscall(__NR_clock_gettime, CLOCK_THREAD_CPUTIME_ID, &tp)) return 0; return (ulonglong)tp.tv_sec*10000000+(ulonglong)tp.tv_nsec/100; -#endif /* HAVE_CLOCK_GETTIME */ -#else /* HAVE_THREAD_CPUTIME_ID */ +#endif /* CLOCK_THREAD_CPUTIME_ID */ return 0; -#endif } |