----- Ursprüngliche Nachricht -----
Von: Bruce Olney
Gesendet am: 07 Okt 2010 18:20:22

>> ...I don't use mspgcc4 as it isn't ready for critical production 
>> environment...

> This was timely.  I'm about to begin a critical production project using an
> MSP430.  I was planning on starting with mspgcc4 as the chosen compiler.

Starting with mspgcc4 isn't that much of a problem. The problem is moving
from mspgcc3 to mspgcc4 with an existing and tested codebase
(libraries, applications).

In my case, development started years before even the idea of mspgcc4 was born.

> If you don't mind my asking, what does mspgg4 lack to be ready for a
> critical production environment?

Nothing specifically. For mspgcc3, most compiler bugs are already known.
For mspgcc4, many will still have to be dicovered.
If you need the newer 430x features (larger address range) and don't want to
write your own upper memory handling for data above 64k or need to put code
into that area, then there's no way around mspgcc4 anyway.
Yet this area is still under development.
The other available toolchains (IAR/CCE), while being a bit older and 
commercially developed too, still have the same problems anyway.

> What compilers do you recommend that are ready?  You mentioned using
> mspgcc3; is it ready?

Depending on what you need, mspgcc3 is fine or mspgcc4 is a must.
If you start a new development, you'll have to validate your product anyway, so
it doesn't make much of a difference. It's just easier to identify and fix bugs 
caused by known compiler bugs than to detect new compiler bugs as cause
of a failure.
But even if the compiler would be 100% bug-free, your code may still be faulty
and needs to be thoroughly tested anyway before releasing it. :)

Anyway, the structure of mspgcc (3 and 4) allows you to develop workarounds
much easier than with any other compiler for MSP. If the compiler doesn't do
what you want, feed it with inline-assembly and the sun is shining again.
If done properly, it will not even negatively affect optimization.

JMGross

------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
Spend less time writing and  rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Reply via email to