Skip to content
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

IDF-v4.4.5 build warning in esp_ptr_in_drom (IDFGH-10398) #11653

Closed
3 tasks done
Andste82 opened this issue Jun 12, 2023 · 2 comments
Closed
3 tasks done

IDF-v4.4.5 build warning in esp_ptr_in_drom (IDFGH-10398) #11653

Andste82 opened this issue Jun 12, 2023 · 2 comments
Assignees
Labels
Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally

Comments

@Andste82
Copy link
Contributor

Answers checklist.

  • I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
  • I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

a small bug has sneaked into the IDF v4.4.5, which leads to ugly warnings when building:

/esp-idf/components/soc/include/soc/soc_memory_types.h:140:25: warning: comparison of integer expressions of different signedness: 'intptr_t' {aka 'int'} and 'uint32_t' {aka 'unsigned int'} [-Wsign-compare]
     return ((intptr_t)p >= drom_start_addr && (intptr_t)p < SOC_DROM_HIGH);
             ~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
@espressif-bot espressif-bot added the Status: Opened Issue is new label Jun 12, 2023
@github-actions github-actions bot changed the title IDF-v4.4.5 build warning in esp_ptr_in_drom IDF-v4.4.5 build warning in esp_ptr_in_drom (IDFGH-10398) Jun 12, 2023
@laukik-hase
Copy link
Collaborator

Hello, @Andste82!

Thank you for sending the issue report. I was investigating this issue but unfortunately could not reproduce it on the ESP-IDF v4.4.5 tag.

We have suppressed all Wsign-compare warnings here - are you using any special C/CXX flags while compiling your example?

@Andste82
Copy link
Contributor Author

Hi @laukik-hase
thanks for you're response.

i use "vanilla" cmake in my projects because i don't like the "component magic" when using idf.py very well.
since the file with the warning is a header file, it is possible that my libs, with unsuppressed warnings, includes it.

i usually build my libs as follows:

target_compile_options(fancylib
	PRIVATE -Wall -Wextra -Wno-unused-parameter
)

the warning is not too bad, but since i want to handle every warning, and the headerfile is often included, the waning pops up very often during the build process.

@espressif-bot espressif-bot added Status: In Progress Work is in progress Status: Done Issue is done internally Resolution: NA Issue resolution is unavailable and removed Status: Opened Issue is new Status: In Progress Work is in progress labels Jul 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally
Projects
None yet
Development

No branches or pull requests

4 participants