Bug #99365 Regression of incorrect InnoDB mutex atomics implementation ?

• Submitted: 27 Apr 2020 4:17
• Modified: 27 Apr 2020 12:45
• Reporter: Bryan Nunweek
• Status: Unsupported
• Category: MySQL Server
• Severity: S2 (Serious)
• Version: 5.6.47
• OS: MacOS (Leopard 10.5.8)
• CPU Architecture: POWER (Macports)

[27 Apr 2020 4:17] Bryan Nunweek

Description:
Sometime since 5.6.45 it seems that this old bug may have been reintroduced:

https://bugs.mysql.com/bug.php?id=72539

Key lines from log:

/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mysql56/mysql56/work/mysql-5.6.47/storage/innobase/include/sync0sync.ic: In function ‘lock_word_t ib_mutex_test_and_set(ib_mutex_t*)’:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mysql56/mysql56/work/mysql-5.6.47/storage/innobase/include/sync0sync.ic:91: error: ‘os_atomic_test_and_set’ was not declared in this scope
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mysql56/mysql56/work/mysql-5.6.47/storage/innobase/include/sync0sync.ic: In function ‘void mutex_reset_lock_word(ib_mutex_t*)’:
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mysql56/mysql56/work/mysql-5.6.47/storage/innobase/include/sync0sync.ic:120: error: ‘os_atomic_clear’ was not declared in this scope

Reported at macports.org as:

https://trac.macports.org/ticket/60400 with full log.

How to repeat:
sudo port install mysql56-server on a G5 running Leopard :-)

Suggested fix:
Reimplement fixes described in:

https://bugs.mysql.com/bug.php?id=72539

[27 Apr 2020 12:45] MySQL Verification Team

Hi Mr. Nunweek,

Thank you for your bug report.

I fully understand that you might see a problem on the POWER CPU on the old OS X Leopard.

However, the bug that you mentioned is fixed. However, the platform that you are using is not supported for quite some time, which is why you are able to seeing the problem.

Only macOS on Intel is supported, which is the one I am using.