Suppress spurious warnings from the CCS compiler #444
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
@jscott-hotstart Thanks a lot for adding support for this board and compiler! It seems like CCS gets confused by the creative use of |
jonathangjertsen
changed the title
Member
|
@jonathangjertsen, thanks a lot for taking the time to create a PR. We'll look into it and proceed with merging if all goes well. Thanks, |
jscott-hotstart
approved these changes
Apr 5, 2022
Contributor
There was a problem hiding this comment.
I've tested these changes and they do indeed suppress the warnings as advertised. Thanks @jonathangjertsen!
AniruddhaKanhere
approved these changes
Apr 5, 2022
paulbartell
approved these changes
Apr 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Supress spurious warnings from the CCS compiler
Description
Fixes warnings when building with CCS:
error #1916-D: definition at end of file not followed by a semicolon or a declaratorTest Steps
Compile a project with this fix, and the warning should go away
Related Issue
N/A
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.