• State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 21 subscribers
  • Views 2511 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

PC-Lint, uV3, infineon C515C

Greg Elkin

I believe I've got PC-Lint installed OK as per the Keil instructions, but on Linting my source it seems all the system sfr & sbits are being flagged up, eg :

"Error 40: Undeclared identifier 'ADCON'"


along with TMOD, TH0, TL0, EAL, ET0, P1, P3, P4...

These are resolved for the compiler by a

#include <reg515c.h>


Keil include file with SBIT and SFR definitions in. Lint doesn't seem to be seeing them though.

Does anyone have any pointers for me for how to fix this?

Parents
  • 0 in reply to Greg Elkin

    I'd have to crack the spec to be sure what standard behavior really is -- if it's not just "implementation defined".

    But in my mind, #include "" means search the directory containing the including file, then the 'path', while #include <> means search the 'path'. The 'path' is defined by tool-specific means: -i for PC-Lint (and for most compiler command lines).

    So it would seem that there's something wrong with the definition of the path. Changing to "" and moving the file to the project root works because of that first step in "" processing. But lint should be able to find the file in the installation directory.

    See Section 6.1 of the PC-Lint manual for a discussion of "library" headers. #include<> is one of the ways lint assumes that a .h file is a "library" header, and thus knows not to complain about unused items in the header. #include"" is not automatically a library header. So, if you want to keep using #include "" for the register.h, then you might want to use +libdir or +libh to mark that directory/file as a library header.

    (One of the nice things about PC-Lint is that it's very configurable. One of the bad things about PC-Lint is that it's very configurable...)

Reply
  • 0 in reply to Greg Elkin

    I'd have to crack the spec to be sure what standard behavior really is -- if it's not just "implementation defined".

    But in my mind, #include "" means search the directory containing the including file, then the 'path', while #include <> means search the 'path'. The 'path' is defined by tool-specific means: -i for PC-Lint (and for most compiler command lines).

    So it would seem that there's something wrong with the definition of the path. Changing to "" and moving the file to the project root works because of that first step in "" processing. But lint should be able to find the file in the installation directory.

    See Section 6.1 of the PC-Lint manual for a discussion of "library" headers. #include<> is one of the ways lint assumes that a .h file is a "library" header, and thus knows not to complain about unused items in the header. #include"" is not automatically a library header. So, if you want to keep using #include "" for the register.h, then you might want to use +libdir or +libh to mark that directory/file as a library header.

    (One of the nice things about PC-Lint is that it's very configurable. One of the bad things about PC-Lint is that it's very configurable...)

Children