Bug#190399: Bug#246547: amd64 support for glibc 2.3.2.ds1-14
On Thu, Jul 08, 2004 at 05:07:14PM +0200, Goswin von Brederlow wrote:
> GOTO Masanori <gotom@debian.or.jp> writes:
> > BTW, I concerned gcc multilib + gcc 3.4 support. This may be not
> > happened in sarge. I wait to put the modification of #252720 until
> > the request is come. If we want to release sarge soon, and if we want
> > to put amd64 into sarge, then it's good idea to keep gcc 3.3, IMHO.
> > What's the merit of pushing gcc 3.4 into sarge on amd64?
>
> gcc3.4 has better amd64 support (mainly faster). A handfull of
> compiler ICE are fixed while a handfull of c++ incompatibilites will
> probably show up and cause FTBFS.
>
> The fixed and new bugs probably even out so the remaining argument
> would be speed.
>
> Starting with gcc-3.4 would also save the gcc 3.3 -> 3.4 transition
> but the rest of debian will have to do that anyway so we save nothing.
The rest of Debian probably won't be doing this for sarge. The C++ ABI
transition is difficult and requires library package renaming; I
recommend staying with g++ 3.3, even if it's a little painful.
--
Colin Watson [cjwatson@flatline.org.uk]
Reply to: