> If the gcc maintainers think that pointing g++ at g++-3.4 on these archs is
> the best option, I'm game. One disadvantage is that it wouldn't let us get
> feedback about what else might be wrong with g++-4.0 on those architectures,
> but we probably already have all the information we're going to get about
> the current round of toolchain packages.
The point I'm making is that it's a *release critical* bug. The
relevant gcc should not be in testing on those archs.
Steve Langasek <email address hidden> writes:
> If the gcc maintainers think that pointing g++ at g++-3.4 on these archs is
> the best option, I'm game. One disadvantage is that it wouldn't let us get
> feedback about what else might be wrong with g++-4.0 on those architectures,
> but we probably already have all the information we're going to get about
> the current round of toolchain packages.
The point I'm making is that it's a *release critical* bug. The
relevant gcc should not be in testing on those archs.