Calvin Chan

not quite fully fixed. As seen from the following link: https://sourceforge.net/p/cppcheck/discussion/general/thread/8f618cb0a3/ for case of array of variable at absolute address. Calvin

Hi New release 1.86 has taken care of some of the non-standard compiler extension that I raised few days ago. Nevertheless, some are not addressed. e.g. the @inline keyword @inline void dummyFunc(void) {} nor the absolute address on array declaration. volatile unsigned char ADC_DBR[20] @0x53e0; // data buffer registers Furthermore, I would expect the following sample code with different outcomes: volatile unsigned char volatileRegister ; void main(void) { unsigned char i = 100 ; volatileRegister...

further to my previous message, one more culprit on @ is: `#define INLINE_STATIC_FUNC @inline static INLINE_STATIC_FUNC void softwareReset(void) { } or alternatively @inline static void softwareReset(void) { } `

hi The @ non-standard compiler extension is not quite done. The array of characters at absolete address is one of the culprits. Consider the following code snipplet: volatile unsigned char ADC_DBR[20] @0x53e0; / data buffer registers / void main(void) { unsigned char i = 100 ; static unsigned char dummy ; for(i = 0 ; i < 10 ; i++) {} } Calvin

Hi Daniel Your guess is confirmed. By adding the include path .\Header, all the c files become invalid. Somehow the header files get cppcheck confused. But there is no hint from cppcheck to pinpoint the problem. That makes this situation unsolvable. Calvin

Hi Daniel Funny enough though. I have put all the headers into a sub-folder called header, and the source c files into a sub-folder called source, and the parent folder called temp. cppcheck onto temp folder gives me no problem. But when I move all headers and sources just into temp folder and remove the sub-folders, all the sources give errors - at line 0, with summary of syntax error. As usual, the first part of the sources are many lines of comments before the actual code comes into. see attached....

bingo. This works so far. Thanks for support. Calvin

I am just a windows user and I have no idea on how to build your temp. release to make up the pre-release version. Calvin