English
[解決済] Warning Messages from GCC for Renesas RX Compiler : _getpid, _kill
Warning Messages from GCC for Renesas RX Compiler : _getpid, _kill
サポートご担当者様
I hope this message finds you well. I am writing to inquire about warning messages that I am encountering while using the GCC for Renesas RX compiler.
Specifically, when compiling C programs for the RX651 microcontroller, I am receiving the following warnings:
warning: _getpid is not implemented and will always fail
warning: _kill is not implemented and will always fail
I understand that these warnings pertain to the _getpid and _kill functions not being implemented.
However, I would appreciate further clarification on why these functions are not implemented and whether there are any plans to address this in future releases of the compiler.
Additionally, I primarily use e2 Studio version 23_07 for my development tasks. When I enable the Linker Option –specs=nano.spacs, I notice that warnings transform into errors, providing a clearer indication of potential issues. However, upon upgrading to e2 Studio version 24_01, I have observed that warnings persist even with the same Linker Option enabled.Could you kindly provide some insight into why this discrepancy exists between versions? Is there a specific reason why warnings remain in version 24_01 despite the Linker Option being enabled? Additionally, I would appreciate any guidance on how to address this issue or whether there are any updates or patches planned to address it in future releases.
Thank you for your attention to this matter. I look forward to your response.
よろしくお願いいたします。
ベストアンサー
Hello,
Thank you for reaching out to us!
The warnings are generated by the stub implementations of the mentioned functions (getpid, kill, wait, …). These stub implementations provide no functionality beside allowing the link process to complete. These functions are system calls, which in a bare-metal project must be provided by the user,
thus there are no plans to implement real versions for them.
The observed difference between e2 Studio 202307 and e2 Studio 202401 is due to a bug fix made in version 202311.
As stated in the GCC manual (<toolchain install location>/Doc/gcc.pdf):
-specs=specs To use newlib-nano, the users should provide the ‘-specs=nano.specs’ option in addition to the gcc compile and link time options. If ‘-msim’ is used, the ‘-specs=nano.specs’ option will be accompanied by the ‘-specs=sim.specs’. Otherwise, the ‘-specs=lnosys.specs’ option should be passed along the ‘-specs=nano.specs’ option.
Before e2 Studio 202311, checking the –specs=nano.specs linker option did not result in passing the -specs=lnosys.specs option too. This meant that not even stub implementations were provided to the linker, resulting in link errors.
Please let us know if we can be of further assistance.
__
Best regards,
The Open Source Tools Team
-
RTani -
Dear The Open Souce Tools Team,
I would like to express my gratitude for your prompt and informative response regarding the issues I encountered with e2 Studio. Your explanation helped me understand the differences in build results between different versions of the software.
Following your guidance on setting the linker options, I was able to achieve consistent results across different versions of e2 Studio.
Moreover, I appreciate your advice on adding the kill and getpid functions to address the warning messages. By implementing these functions, I successfully resolved the warnings.
Once again, thank you for your assistance.
