Bug #77637 | mysql 5.6.25 compiled warning | ||
---|---|---|---|
Submitted: | 7 Jul 2015 10:11 | Modified: | 7 Jul 2015 12:12 |
Reporter: | jacky chen | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Compiling | Severity: | S3 (Non-critical) |
Version: | 5.6.25 | OS: | CentOS (6.3 x86_64) |
Assigned to: | CPU Architecture: | Any |
[7 Jul 2015 10:11]
jacky chen
[7 Jul 2015 10:12]
jacky chen
mysql 5.6.25 compiled warning
[7 Jul 2015 12:12]
MySQL Verification Team
Hello jacky chen, Thank you for the report. Thanks, Umesh
[10 Aug 2015 14:53]
Tor Didriksen
Posted by developer: This is actually intentional, comments in the code: /* We needn't initialize: bound_sj_equalities - protected by try_loosescan quick_max_loose_keypart - protected by quick_uses_applicable_index best_loose_scan_key - protected by best_loose_scan_cost != DBL_MAX best_loose_scan_records - same best_max_loose_keypart - same best_loose_scan_start_key - same Not initializing them causes compiler warnings with g++ at -O1 or higher, but initializing them would cause a 2% CPU time loss in a 20-table plan search. So we initialize only if warnings would stop the build. */ To silence it, you can run cmake with -DMYSQL_MAINTAINER_MODE=1