On Wed, Jul 13, 2016 at 11:09 AM, William Hermans <[email protected]> wrote: > > Granted, now, I've read that redhat was contracted to build a newer gcc port > a few years back, and that this gcc is actually used by CCS now days( for > the MSP430 toolchain ). It is purported to support the newer MSP430G2 > variants, among others, but still is not as reliable as the gcc toolchain it > was meant to replace.
Well, it replaced both CCS and the old MSP430 GCC, and I think the concensus is that it's for the good. There were issues in the beginning, but now it's being worked on by both RedHat and TI, and nobody recommends the old stuff for use any more. The usual argument for GCC is that it's relentlessly getting better; proprietary alternatives tend to lose their initial advantage because GCC contributors have a look at the differences and implement the improvements. Look how far Dimitar got it, working on his own. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAC%3D1GgGH-eijzdkeyj9cL8O9jiGJj2QZ0L%3DqPNRFbH7%2B2R6cuQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
