How to continue compilation after the first error message?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to continue compilation after the first error message?

1,909 Views
davide_ferrari
Contributor II

Hi everybody,

I'm using CodeWarrior for HCS12(X) Microcontrollers V5.0

 

I'd like to perform a compiler validation, expecially for MISRA-C 2004 compilance.

 

The problem I'm facing is that the compiler stops the compilation after the first error message in a file.

 

Is there a way to force the compilation to complete the file parsing until the end?

 

I'd like to avoid the setting of all error messages as "warnings" if possible...

 

Many thanks

Davide

Labels (1)
Tags (1)
0 Kudos
Reply
3 Replies

1,327 Views
davide_ferrari
Contributor II

Thanks for your comment...

I agree with everything..

What I'm trying to do is to understand whether the compiler checks some rules not checked by PCLint... so far I've found a couple of them, so it was worth trying... 

D

0 Kudos
Reply

1,327 Views
slarti
Contributor I

davide.ferrari wrote:

What I'm trying to do is to understand whether the compiler checks some rules not checked by PCLint... so far I've found a couple of them, so it was worth trying... 

D


Hi Davide,

care to list a few of those not checked by PCLint? I am very interested in what PCLint misses vs. the compiler - although I admit that I am not too enthusiastic about MISRA in general.

 

best wishes

Mark

 

0 Kudos
Reply

1,327 Views
slarti
Contributor I

Sorry to say it rather directly, but your request doesn't make too much sense. Although there may have been reasons to contiue compilation on erroneous input back then in the 60's (mainly in the face of batch systems and precious machine time), today most of these have gone away or are even reversed, with the compiler notifying the programmer immediately instead of wasting a 10-minute build.

 

What you want is a professional MISRA checker which does no compilation but just a parse run. PCLint comes to mind but there are others, and most of them are dirt cheap given the value (savings in debugging effort) they represent.

 

regards,

Mark 

0 Kudos
Reply