-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Compiler warnings make test-linux
workflow fail on v14.x
#38718
Labels
c++
Issues and PRs that require attention from people who are familiar with C++.
Comments
targos
added
c++
Issues and PRs that require attention from people who are familiar with C++.
v14.x
labels
May 18, 2021
|
RaisinTen
added a commit
to RaisinTen/node
that referenced
this issue
May 18, 2021
`offset` and `max_length` can be initialized to `0` to avoid the warnings from `-Wmaybe-uninitialized`. Fixes: nodejs#38718
I see similar errors locally (Fedora 33 with gcc/g++ 10) with master.
|
Interesting. I do not see any errors with GCC 8.4 (CentOS 8) |
On CentOS Stream release 8 I do not get errors with either the default GCC 8.4 or GCC 9.2 (via gcc-toolset-9) but do get them with GCC 10.2 (gcc-toolset-10). |
RaisinTen
added a commit
to RaisinTen/node
that referenced
this issue
May 19, 2021
The variables could be initialized to `0` to avoid the warnings from `-Wmaybe-uninitialized`. Fixes: nodejs#38718
targos
pushed a commit
that referenced
this issue
May 25, 2021
The variables could be initialized to `0` to avoid the warnings from `-Wmaybe-uninitialized`. Fixes: #38718 PR-URL: #38722 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Minwoo Jung <[email protected]>
danielleadams
pushed a commit
that referenced
this issue
May 31, 2021
The variables could be initialized to `0` to avoid the warnings from `-Wmaybe-uninitialized`. Fixes: #38718 PR-URL: #38722 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Minwoo Jung <[email protected]>
targos
pushed a commit
that referenced
this issue
Jun 5, 2021
The variables could be initialized to `0` to avoid the warnings from `-Wmaybe-uninitialized`. Fixes: #38718 PR-URL: #38722 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Minwoo Jung <[email protected]>
targos
pushed a commit
that referenced
this issue
Jun 11, 2021
The variables could be initialized to `0` to avoid the warnings from `-Wmaybe-uninitialized`. Fixes: #38718 PR-URL: #38722 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Minwoo Jung <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For example: https://github.com/nodejs/node/runs/2607695302?check_suite_focus=true
Some notes:
master
--error-on-warn
was backported to v14.3.0 so this is probably a regression in one of the commits that were backported to v14.17.The text was updated successfully, but these errors were encountered: