-
Notifications
You must be signed in to change notification settings - Fork 11
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
Makefile.uk: Don't add unsupported warnings when built with clang #10
base: staging
Are you sure you want to change the base?
Conversation
Hackathon points: 20 |
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.
Thank you @iAmGroute, besides the comments. please also add a short description to the commit message.
@iAmGroute, could you please take care of the comments above? |
Hi @StefanJum, sorry for the delay. For reference, when built:
I've tested the above with GCC and Clang, it's as expected:
Versions:
|
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.
Hi @iAmGroute, please wrap your commit message at ~72 characters.
Also it looks like there are some conflicts, so please rebase it. We can merge it after that.
Clang (12.0.0) does not recognize the warnings: no-unused-but-set-variable no-maybe-uninitialized no-builtin-declaration-mismatch It would print "unknown warning option" warning messages. These should be enabled only with GCC (tested with 11.3.0). GitHub-Fixes: unikraft#1 Co-authored-by: Nikos Oikonomou <[email protected]> Signed-off-by: Nikos Oikonomou <[email protected]> Signed-off-by: Groute <[email protected]>
Should be OK now. |
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.
All good now, thanks.
Reviewed-by: Stefan Jumarea [email protected]
Part of the hackathon challenges, Fixes: #1
I couldn't reproduce the original issue with
-Wno-unused-but-set-variable -Wno-maybe-uninitialized
, but verified with-Wno-builtin-declaration-mismatch
.Authored by @Se7enBit, I'm just doing the commit/PR :)