-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[LTO - DQM] Compiler warnings -Wodr and -Wstrict-overflow in dqm category #38679
Comments
A new Issue was created by @aandvalenzuela Andrea Valenzuela. @Dr15Jones, @perrotta, @dpiparo, @rappoccio, @makortel, @smuzaffar, @qliphy can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign dqm |
New categories assigned: dqm @jfernan2,@ahmad3213,@micsucmed,@rvenditti,@emanueleusai,@pmandrik you have been requested to review this Pull request/Issue and eventually sign? Thanks |
As pointed out in #38685, the
|
@smuzaffar While trying to understand some of these
from GCC 8 release notes (pointed in https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1635615) We already include |
good point @makortel . For now, we are not passing |
Ok, but we see warnings from signed integer overflow like
I found from Clang's manual that
(GCC's manual is not v, but they refer to the Clang's manual of the sanitizer) |
ok, so lets drop |
full cmssw PR tests with out
if no objections then I can merge cms-sw/cmsdist#8026 to drop |
closing as cms-sw/cmsdist#8026 has been merged |
Hello,
We have seen some compiler warnings of the type
-Wodr
and-Wstrict-overflow
in LTO_X IBs (CMSSW_12_5_LTO_X_2022-07-07-1100 and CMSSW_12_5_LTO_X_2022-07-06-1100, for example) in some packages of thedqm
category. See sample stack trace:DQM/HLTEvF
reports-Wodr
warning:Validation/MtdValidation
reports-Wodr
warning:Validation/Geometry
reports-Wstrict-overflow
warning:These warnings are present also in other packages, such as reported in #38650 (It seems there are some elements defined multiple times within the same namespace leading to violation of the C++ One Definition Rule) and #38649 (Signed overflow could occur under certain conditions). Could you please have a look at it?
Many thanks,
Andrea.
The text was updated successfully, but these errors were encountered: