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 *manually* but if those values are
> > the *defaults*, it's more likely that people will use them and will
> > identify build problems if they exist.
> >
> >   i think it's more valuable to push the toolchain along, just so if
> > there are issues hiding in the newer versions, they're identified as
> > quickly as possible.
> >
>
> The reason why we stick to 4.1.2 is simply the fact that it compiles
> good code. 4.2 is broken on ARM, misscompiles some stuff on x86, not
> to mention that probably noone tested all platforms out there. We
> slowly bumb toolchain versions when the toolchain is known to work
> nicely for some time for a developer.

ok, i didn't realize the situation WRT to gcc.  but is there anything
stopping upgrading the default of binutils to 2.18?  does that not
work well with any of the architectures?

as i mentioned before, unless there's an actual issue, i'm a big fan
of pushing version upgrades so that any problems can be identified
sooner rather than later.  if a newer version of some toolchain
component works on all but one architecture, i think it's more useful
to bump the default version, except in the case of that one
architecture (which is what the binutils Config.in would be doing
anyway WRT to avr32, which doesn't have patches for binutils-2.18).

anyway, just my $0.02.

rday

p.s.  and what about gdb?  currently, it's sitting at 6.3 while 6.7.1
is out.
--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to