-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Core code should compile without warnings. #77
Comments
Hi @KurtE , |
I pushed some of the changes needed as part of my Draft PR #90 There were a few warrnings, where signed versus unsigned as some of the values were defined as - numbers to a type and compared to a variable that is uint32_t. Plus did attempt to get to the printf one where %X and variable passed was signed. |
Adapt to changed function signatures in TinyUSB
Resolves arduino#77 At least partially. I did not go into the API class to fix the printf statement issue.
Adapt to changed function signatures in TinyUSB Former-commit-id: 5ef8470
As I mentioned on the memory corruption issue, as a general practice, I don't want to see any compiler warnings, in my builds, even with the full or all warnings option turned on. Often times Warnings give you a hint on what might be wrong.
But your mind gets unsensitized to it, when you see them with every build. So you might miss ones that actually might help localize an issue.
With the current board release, I see warnings in at least two of the source files:
And:
My quick look through I don't see anything obvious that is impacting the memory corruption bug, but...
The text was updated successfully, but these errors were encountered: