On Thu, 27 Mar 2008, Imre Kaloz wrote:
On 2008.03.27. 23:03:59 Robert P. J. Day [EMAIL PROTECTED] wrote:
is there any inherent difficulty in bumping up the software versions
of the toolchain components? say, binutils to 2.18 and gcc to 4.2.3?
i realize you can always do that
On Thu, 27 Mar 2008, Imre Kaloz wrote:
On 2008.03.27. 23:37:47 Luigi 'Comio' Mantellini [EMAIL PROTECTED] wrote:
snip
Ok. Anyway the compiler gcc4.3 supports a lot new cpus (like the
coldfire) :) opening new development horizons.
Sure, as AVR32 uses gcc 4.2.3.. Some targets work
is there any inherent difficulty in bumping up the software versions
of the toolchain components? say, binutils to 2.18 and gcc to 4.2.3?
i realize you can always do that *manually* but if those values are
the *defaults*, it's more likely that people will use them and will
identify build
On 2008.03.27. 23:03:59 Robert P. J. Day [EMAIL PROTECTED] wrote:
is there any inherent difficulty in bumping up the software versions
of the toolchain components? say, binutils to 2.18 and gcc to 4.2.3?
i realize you can always do that *manually* but if those values are
the *defaults*,
On 2008.03.27. 23:37:47 Luigi 'Comio' Mantellini [EMAIL PROTECTED] wrote:
snip
Ok. Anyway the compiler gcc4.3 supports a lot new cpus (like the
coldfire) :) opening new development horizons.
Sure, as AVR32 uses gcc 4.2.3.. Some targets work better with newer
compilers, others do not. Spice
On gio, 2008-03-27 at 23:42 +0100, Imre Kaloz wrote:
On 2008.03.27. 23:37:47 Luigi 'Comio' Mantellini [EMAIL PROTECTED] wrote:
snip
Ok. Anyway the compiler gcc4.3 supports a lot new cpus (like the
coldfire) :) opening new development horizons.
Sure, as AVR32 uses gcc 4.2.3.. Some
