Free Windows C Compile that give good warning?

This is a discussion on Free Windows C Compile that give good warning? within the C Programming forums, part of the General Programming Boards category; I am working on an embedded project that uses a C-like compiler (Rabbit Dynamic C 9.6) and I wish to ...

  1. #1
    Registered User
    Join Date
    May 2009
    Posts
    2,544

    Free Windows C Compile that give good warning?

    I am working on an embedded project that uses a C-like compiler (Rabbit Dynamic C 9.6) and I wish to speed up the Edit/Build/Test Cycle.

    I have decided to use an Windows C Compiler to test my code for valid syntax and operation in some cases.

    I am looking for C Compiler that give good warnings for non standard code.

    I am currently testing MinGW GCC, Watcom, and LLVM C compliers.
    I plan to add Pelles C Compiler to my list of test Compilers.

    Is there any other C Compilers that I should consider?

    I have tried SDCC and Digital Mars C compilers and decided they would require to much work to get the project code to successfully compile.

    Tim S.

  2. #2
    Banned
    Join Date
    Aug 2010
    Location
    Ontario Canada
    Posts
    9,547
    If you go into the project settings in PellesC and set the warnings level to high, it will drive you positively crazy with all the stuff it tells you about. It is very comprehensive.

    Also, you should give some thought to how much time you could waste getting it working on C when you have to ultimately get it working on RD... They are very alike, but not the same. Is there no way to produce a higher level of warning in the code's final compiler?

  3. #3
    Registered User
    Join Date
    May 2009
    Posts
    2,544
    Quote Originally Posted by CommonTater View Post
    Is there no way to produce a higher level of warning in the code's final compiler?
    I have been using MinGW GCC for about a year to generate Compiler Warnings; it has taken me the past 2 days to get it to link using MinGW.

    The main warning, that decided me to use MinGW GCC was printf string format checking for right variable type.
    I wasted 4 hours because I did not see a printf problem; so I spent my free time for several days getting the code to compile using MinGW GCC.

    Rabbit DC 9 does not really give good warnings; and I hope to port to a real C Compiler in the future.
    A example of how much it is NOT a C Compiler, Rabbit DC 9 does NOT support "#include".

    Rabbit DC 10 does support "#include", so I hope to port some of the source code to it or a real C Compiler in the future.

    Using an Windows C Compiler, I hope to save about 3 to 5 minutes time downloading the binary into the MCU. Part of the project uses an serial LCD display, I hope to save a lot of time spent doing minor adjustment of the appearance of LCD display.

    I also wish to do unit tests of several functions on a PC platform.

    Tim S.
    Last edited by stahta01; 11-24-2010 at 08:37 PM.

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. classes and objects
    By GoldenBoy in forum C++ Programming
    Replies: 12
    Last Post: 07-08-2010, 07:28 AM
  2. Compile crashes certain windows
    By Loduwijk in forum C++ Programming
    Replies: 5
    Last Post: 03-26-2006, 08:05 PM
  3. Compiler "Warnings"
    By Jeremy G in forum A Brief History of Cprogramming.com
    Replies: 24
    Last Post: 04-24-2005, 01:09 PM
  4. Interface Question
    By smog890 in forum C Programming
    Replies: 11
    Last Post: 06-03-2002, 05:06 PM
  5. i need links to good windows tuts...
    By Jackmar in forum Windows Programming
    Replies: 3
    Last Post: 05-18-2002, 11:16 PM

Tags for this Thread


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21