On Wed, 12 Mar 2003, Szakacsits Szabolcs wrote:
> On Wed, 12 Mar 2003, Szakacsits Szabolcs wrote:
> > On Wed, 12 Mar 2003, Richard Henderson wrote:
> > > > This bug is in most 2.95, 2.96 and according to Alan in 3.0 and early
> > > > 3.1) and people would just start "working around" it by commenting out
> > > > the check for getting something to work quickly then forgetting about
> > > > the issue completely.
> > >
> > > The bug report I can find,
> > >
> > > http://gcc.gnu.org/ml/gcc-patches/2001-06/msg00746.html
> > >
> > > was fixed before gcc 3.0.0 was released. So if this is
> > > a different bug...
Some data points, in time order.
SuSE 8.0 2.95.3-216 no bug yet [1]
Debian 3.0 2.95.4-14 no bug yet [1]
Red Hat 7.[23] 2.96-81 no bug yet [2,3]
Red Hat 7.[23] 2.96-98 bug introduced [2,3]
Mandrake 8.1 2.96-0.62mdk bug introduced [4]
Red Hat 7.[23] 2.96-103 bug fixed [2,3]
SuSE 8.0 3.0.4 (SuSE) bug fixed [1]
Mandrake 9.1 3.2.2-2mdk bug fixed [1]
[1] I checked
[2] http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=57760
[3] https://rhn.redhat.com/errata/RHBA-2002-055.html
[4] http://bugme.osdl.org/show_bug.cgi?id=432
So it's not so serious as we first thought. Probably the "halt build
if broken compiler detected" approach is enough.
Szaka
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Mar 15 2003 - 22:00:31 EST