HostedRedmine.com has moved to the Planio platform. All logins and passwords remained the same. All users will be able to login and use Redmine just as before. "Read more...":https://support.plan.io/news/187
Bug #868533
closedclang-10 tautological-compare warnings
0%
Description
Some warnings seen when compiling with clang-10. I were compiling S3_0, but likely all branches are affected.
Will attach logs later.
Files
Updated by Marko Lindqvist almost 3 years ago
- Blocks Task #851229: S3_0 alpha4 added
Updated by Marko Lindqvist almost 3 years ago
- File errors.log errors.log added
- Category set to General
These tautological-compare errors come from generated sources (packets_gen.c, specenum_gen.h)
Either we need to fix the code generation (if it can be made safely) or to disable tautological-compare warnings.
Updated by Marko Lindqvist almost 3 years ago
- Subject changed from clang-10 warnings to clang-10 tautological-compare warnings
Well, we already disable tautological-compare warnings, but apparently clang-10 does not care about it. Consider this a compiler bug? I don't have any good ideas for a workaround.
Updated by Marko Lindqvist almost 3 years ago
- Blocks deleted (Task #851229: S3_0 alpha4)
Updated by Marko Lindqvist almost 3 years ago
- Sprint/Milestone set to 2.6.3
Ubuntu-20.04 LTS has clang-10, and warnings (or errors with --enable-debug) are coming up from all branches. However, there the warning seems to be more fine-grained type than already disabled tautological-compare, so we may can fix it by disabling that specific warning.
Updated by Marko Lindqvist almost 3 years ago
After some testing with different compiler commandlines makes me suspect that the problem is in order of the parameters. We set -Wno-tautological-compare before -Wall. Latter again enables the warning that former had disabled.
Updated by Marko Lindqvist almost 3 years ago
- File 0006-debug.m4-Set-always-active-compiler-flags-last-not-f.patch 0006-debug.m4-Set-always-active-compiler-flags-last-not-f.patch added
- Status changed from New to Resolved
Updated by Marko Lindqvist almost 3 years ago
- Status changed from Resolved to Closed
- Assignee set to Marko Lindqvist
Updated by Marko Lindqvist over 2 years ago
- Sprint/Milestone changed from 2.6.3 to 2.6.2.1