• Locked Locked
  • Replies 4 replies
  • Subscribers 119 subscribers
  • Views 5067 views
  • Users 0 members are here
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

How to make ARM compiler report compilation warnings, as error?

Tarun Tarun
Note: This was originally posted on 24th November 2008 at http://forums.arm.com

I want the compiler to report all compilation warnings as errors, in ARM C Compiler. Didn't get any help from the Specs. Has anyone tried this? How can I do it?
Parents
  • Note: This was originally posted on 27th November 2008 at http://forums.arm.com

    I want the compiler to report all compilation warnings as errors, in ARM C Compiler. Didn't get any help from the Specs. Has anyone tried this? How can I do it?

    I guess warnings are issued when we don't comply with the syntax of the language we use. And if you want it as an error, you can try this as well. from RVCT Compiler Reference Guide, command line options :

    When --strict is in force and a violation of the relevant ISO standard occurs, the compiler issues an error message.
    The severity of diagnostic messages can be controlled in the usual way.
    Example:
    void foo(void)
    {
        long long i; /* okay in non-strict C90 */
    }
    Compiling this code with --strict generates an error.

    good luck
    cheers
    Aj
Reply
  • Note: This was originally posted on 27th November 2008 at http://forums.arm.com

    I want the compiler to report all compilation warnings as errors, in ARM C Compiler. Didn't get any help from the Specs. Has anyone tried this? How can I do it?

    I guess warnings are issued when we don't comply with the syntax of the language we use. And if you want it as an error, you can try this as well. from RVCT Compiler Reference Guide, command line options :

    When --strict is in force and a violation of the relevant ISO standard occurs, the compiler issues an error message.
    The severity of diagnostic messages can be controlled in the usual way.
    Example:
    void foo(void)
    {
        long long i; /* okay in non-strict C90 */
    }
    Compiling this code with --strict generates an error.

    good luck
    cheers
    Aj
Children
No data