Hi Jürgen,

I am using the mspgcc 3.4 (with GCC 3.3.6) for some time now and could never really figure out why there is 3.4 in the cvs repository alongside with 4.0.2 and 4.1.1?

msp430-gcc-3.2.3 is the one to use, 4.0.2 and 4.1.1 are work in progress.

Whenever I read something about a version 4.x all I see is that people don't get it compiling. People are suggesting to use 3.4 as this is the most recent one. Since 3.4 is missing some functionality
 of the 4.x I was wondering how the project is evolving. Is it
planned to move to 4.x at some point?

There is although finding time (or someone) to do the work on the
machine description file is the hold up at the moment.

As you can also see from my other posting I am missing a special link-time optimization. Compared to other compilers like Crossworks this is not implemented in mspgcc yet. Is there an alternative?

Separate the objects into separate C files as the linker takes adds together single object files to make the final code.

Is there a tool that works like LLVM (http://llvm.org) that seems to
be able to enhance the GNU GCC with the functionality? Or shall I
wait for the feature to be implemented in mspgcc? Don't get me wrong,
I know that mspgcc is non-commercial and that people and working on
it for free.

I don't know what the time frame will be for the V4 version of mspgcc.

Regards,

--
Peter Jansen
STS
Antarctic Division
203 Channel Highway
Kingston
TAS  7050
AUSTRALIA
Phone +61 3 6232 3533

___________________________________________________________________________

   Australian Government Antarctic Division - Commonwealth of Australia
IMPORTANT: This transmission is intended for the addressee only. If you are not 
the
intended recipient, you are notified that use or dissemination of this 
communication is
strictly prohibited by Commonwealth law. If you have received this transmission 
in error,
please notify the sender immediately by e-mail or by telephoning +61 3 6232 
3209 and
DELETE the message.
       Visit our web site at http://www.aad.gov.au/
___________________________________________________________________________

Reply via email to