Getting compile error in C++ project for bad flags -Wno-pointer-sign, -Werror=implicit-int #55490
Labels
Comments
|
@tejlmand, I created the separate bug like you asked. |
tejlmand
added a commit
to tejlmand/zephyr
that referenced
this issue
Mar 7, 2023
Fixes: zephyrproject-rtos#55490 Follow-up: zephyrproject-rtos#53124 Prefix local version of the return variable before calling `zephyr_check_compiler_flag_hardcoded()`. This ensures that there will never be any naming collision between named return argument and the variable name used in later functions when PARENT_SCOPE is used. The issue zephyrproject-rtos#55490 provided description of situation where the double de-referencing was not working correctly. Signed-off-by: Torsten Rasmussen <[email protected]>
|
thanks. |
carlescufi
pushed a commit
that referenced
this issue
Mar 7, 2023
Fixes: #55490 Follow-up: #53124 Prefix local version of the return variable before calling `zephyr_check_compiler_flag_hardcoded()`. This ensures that there will never be any naming collision between named return argument and the variable name used in later functions when PARENT_SCOPE is used. The issue #55490 provided description of situation where the double de-referencing was not working correctly. Signed-off-by: Torsten Rasmussen <[email protected]>
zephyrbot
pushed a commit
that referenced
this issue
Mar 7, 2023
Fixes: #55490 Follow-up: #53124 Prefix local version of the return variable before calling `zephyr_check_compiler_flag_hardcoded()`. This ensures that there will never be any naming collision between named return argument and the variable name used in later functions when PARENT_SCOPE is used. The issue #55490 provided description of situation where the double de-referencing was not working correctly. Signed-off-by: Torsten Rasmussen <[email protected]> (cherry picked from commit 599886a)
zephyrbot
pushed a commit
that referenced
this issue
Mar 7, 2023
Fixes: #55490 Follow-up: #53124 Prefix local version of the return variable before calling `zephyr_check_compiler_flag_hardcoded()`. This ensures that there will never be any naming collision between named return argument and the variable name used in later functions when PARENT_SCOPE is used. The issue #55490 provided description of situation where the double de-referencing was not working correctly. Signed-off-by: Torsten Rasmussen <[email protected]> (cherry picked from commit 599886a)
This was referenced Mar 7, 2023
fabiobaltieri
pushed a commit
that referenced
this issue
Mar 9, 2023
Fixes: #55490 Follow-up: #53124 Prefix local version of the return variable before calling `zephyr_check_compiler_flag_hardcoded()`. This ensures that there will never be any naming collision between named return argument and the variable name used in later functions when PARENT_SCOPE is used. The issue #55490 provided description of situation where the double de-referencing was not working correctly. Signed-off-by: Torsten Rasmussen <[email protected]> (cherry picked from commit 599886a)
nashif
pushed a commit
that referenced
this issue
Mar 28, 2023
Fixes: #55490 Follow-up: #53124 Prefix local version of the return variable before calling `zephyr_check_compiler_flag_hardcoded()`. This ensures that there will never be any naming collision between named return argument and the variable name used in later functions when PARENT_SCOPE is used. The issue #55490 provided description of situation where the double de-referencing was not working correctly. Signed-off-by: Torsten Rasmussen <[email protected]> (cherry picked from commit 599886a)
zephyrbot
pushed a commit
that referenced
this issue
May 13, 2023
Fixes: #55490 Follow-up: #53124 Prefix local version of the return variable before calling `zephyr_check_compiler_flag_hardcoded()`. This ensures that there will never be any naming collision between named return argument and the variable name used in later functions when PARENT_SCOPE is used. The issue #55490 provided description of situation where the double de-referencing was not working correctly. Signed-off-by: Torsten Rasmussen <[email protected]> (cherry picked from commit 599886a)
cfriedt
pushed a commit
that referenced
this issue
May 13, 2023
Fixes: #55490 Follow-up: #53124 Prefix local version of the return variable before calling `zephyr_check_compiler_flag_hardcoded()`. This ensures that there will never be any naming collision between named return argument and the variable name used in later functions when PARENT_SCOPE is used. The issue #55490 provided description of situation where the double de-referencing was not working correctly. Signed-off-by: Torsten Rasmussen <[email protected]> (cherry picked from commit 599886a)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Unable to build C++ projects since
check_set_compiler_propertyalways passes the check.To Reproduce
Steps to reproduce the behavior:
west build -p -b tdk_robokit1 app/Expected behavior
App should build
Impact
This is a stopper for 2 ZDS sample projects we're putting together and will soon be integrated in Chromium's EC
Logs and console output
Environment (please complete the following information):
mainAdditional context
#55418 fixes the issue for me
The text was updated successfully, but these errors were encountered: