Which version of c32 compiler?

[funlw65]

MPIDE IDE from http://chipkit.org contains a free, non-restricted, full-optimization version of C/C++ gcc version. It comes with newlib and a free alternative to PLIB (PLIB is also available).

Which c32 compiler are you planning to use?

Vasi

[David John Barker]

Firewing is a BASIC compiler - language reference here:

http://www.firewing.info/pmwiki.php?n=Firewing.Reference

It's not a "C" compiler. However, it does use a version of GCC to generate the final ASM.

[funlw65]

Firewing is a BASIC compiler - language reference here:

http://www.firewing.info/pmwiki.php?n=Firewing.Reference

It's not a "C" compiler. However, it does use a version of GCC to generate the final ASM.

Yes, that is clear to me as crystal from the beginning as I presume that you use your own "BASIC to C" translator (the easiest way to provide a BASIC compiler without getting too intimate with the 16 and 32 bit architecture - BCX is doing the same). So, I'm asking again, which version of c32 you use? Because the one included in the MPIDE package is the only full open-source with access to full optimizations options (by example, "-Os" with options also for dead code removal if you want) and newlib powered.

[David John Barker]

> Yes, that is clear to me as crystal from the beginning

Sorry, I misunderstood you...

> which version of c32 you use

The Firewing 32 code generator is built from the open source files for the chipKIT compiler. Firewing enables "-O2" by default. As you say, this version gives you full access to code optimization. However, Firewing can also use the standard Microchip offering (XC32) to create your *.hex file. See here for more information:

http://www.firewing.info/pmwiki.php?n=FirewingUser.XC32Toolsuite

In summary

• Firewing uses open source gcc code generator by default
• Firewing can use xc32, if required

[funlw65]

Thank you for the information. Then that is more than great, congratulations and thank you for the BASIC alternative!

[David John Barker]

No problem, I hope you have fun with the compiler...

[gem1144aaa]

Hi

When I use firewing32 compiler for pic32 everything is fine but when i use the microchip32 it compiles ok but the produced code is 0 size
I've tried everything mentioned in the firewing32 site but it didn't work
any suggestions are welcome
regards

[David John Barker]

When did it start doing this? What happens if you build a project in MPLAB directly using XC32? When you say "0" size, is that the IDE reporting "0" or is there no *.hex file generated?

[funlw65]

David, he is referring to the reported code size.there in console in those "gauges". Personally I started with (B18) version and there I observed that. I supposed that you know the issue. The generated .hex file is ok.

[David John Barker]

OK, well I've not seen that before but I tend not to use the MPLAB gauges. If the *.hex file is OK and Firewing is reporting the correct usage (in the MPLAB output window) then I don't think it is anything to worry about...