I've reassigned this bug from the kernel to gcc-4.0 as we feel that the=20
solution chosen in the kernel packaging is not really a fix, but a=20
workaround.
As tests have shown that the problem does not exist when the same kernel=20
is compiled with gcc-3.3, the real bug is likely in gcc-4.0.
I've "found" the bug for 4.0.1-3 after looking at the dates for relevant=20
uploads, but as uploads were quite frequent, I could be off by a version=20
either way.
Message-Id: <email address hidden>
Date: Wed, 7 Sep 2005 22:55:20 +0200
From: Frans Pop <email address hidden>
To: <email address hidden>
Subject: Bug#322723: 'ip route' kernel problem w/ gcc-4.0
--nextPart25582 84.reTYGQfyOX "us-ascii" Transfer- Encoding: quoted-printable Disposition: inline
Content-Type: text/plain;
charset=
Content-
Content-
I've reassigned this bug from the kernel to gcc-4.0 as we feel that the=20
solution chosen in the kernel packaging is not really a fix, but a=20
workaround.
As tests have shown that the problem does not exist when the same kernel=20
is compiled with gcc-3.3, the real bug is likely in gcc-4.0.
I've "found" the bug for 4.0.1-3 after looking at the dates for relevant=20
uploads, but as uploads were quite frequent, I could be off by a version=20
either way.
Please see the bug history for details.
Cheers,
=46JP
--nextPart25582 84.reTYGQfyOX pgp-signature
Content-Type: application/
-----BEGIN PGP SIGNATURE-----
Kwh6ICoQRAjD4AJ 9eXFLRkY1VALorl cEwuPYEG6dgBwCg mXbD 8WQ3Wthc=
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQBDH1O4gm/
w25SpJycs6hkeFk
=Hffb
-----END PGP SIGNATURE-----
--nextPart25582 84.reTYGQfyOX- -