You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The Keil C166 EC++ compiler throws an error for each compilation unit that includes the task.h header file. As you can imagine, this can be many files! It creates a problem where users of the framework I am providing are concerned when they see a warning for each compilation unit. I am unsure if this issue persists in other Keil toolsets, especially since there are so many official ports. Of course the users can ignore this, or I can fork the kernel, but I think that is bad practice.
Target
Custom Infineon XC2287M target
Host
Host OS: Windows 10 Latest corporate image
Version: 1909
To Reproduce
Use Keil C166 compiler
Compile a C++ file with the FreeRTOS headers attached
Expected behavior
You will see a warning that cannot be suppressed stating:
.\FreeRTOS\include\task.h(121): warning: class "xTASK_PARAMETERS" defines no constructor to initialize the following: const member "xTASK_PARAMETERS::pcName"
Additional context
My easy fix on line 124 of task.h in latest git commit:
Describe the bug
The Keil C166 EC++ compiler throws an error for each compilation unit that includes the task.h header file. As you can imagine, this can be many files! It creates a problem where users of the framework I am providing are concerned when they see a warning for each compilation unit. I am unsure if this issue persists in other Keil toolsets, especially since there are so many official ports. Of course the users can ignore this, or I can fork the kernel, but I think that is bad practice.
Target
Host
To Reproduce
Expected behavior
You will see a warning that cannot be suppressed stating:
Additional context
My easy fix on line 124 of task.h in latest git commit:
I found an older post for the same issue, but on the ARM platform here
Unfortunately, I am not able to suppress this warning without globally disabling all warnings (no warning number associated). See this for details.
The text was updated successfully, but these errors were encountered: