Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
cmake: use the warnings_as_errors flag for cpp files #78419
cmake: use the warnings_as_errors flag for cpp files #78419
Changes from all commits
b73da5a
0ee05d9
0ffeb16
283f591
659f210
b57c682
66a71f3
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tempted to have this as part of
DT_REG_ADDR
(and potentiallyDT_REG_SIZE
too) macro itself but that would be a substantial change, definitely worth its own PR, I propose to patch this one up for now. Somewhat surprised CI does not hit more cases of this warning though.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks really odd to me offhand, is the ADDR a 32 bit unsigned or not? If it is, then the DT macro should ensure that's the type being provided. If its not, then .phys_addr should have its type corrected. This looks a bit like a quick fix at the wrong place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's a quick fix, that's pretty much what I meant in the comment above
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please create an issue for this then, if its meant to be revisited
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There already exist an issue:
#53505
I gave it a shot, but gave up:
#70761
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jeppenodgaard what was wrong with that? CI errors? I was considering giving it a go as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fabiobaltieri see this closing comment:
#70761 (comment)
Check notice on line 75 in include/zephyr/sys/device_mmio.h
You may want to run clang-format on this change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like its doing something completely different than it was before? Confused by this change, why is "[n] = " no longer needed, why was it needed before?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no idea why it was introduced originally, I guess to do something with that
n
variable? regardless, the compiler does not like it, the alternative would be to shut off that warning, happy with either. @yperess?Check notice on line 928 in tests/lib/cbprintf_package/src/main.c
You may want to run clang-format on this change