planing to switch x86 to it for 2.6.26.
compiles, boots and works fine here.

please update other archs too for the default Lenny gcc.

thanks

--
maks


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Jun 09, 2008 at 11:51:28PM +0200, maximilian attems wrote:
> planing to switch x86 to it for 2.6.26.
> compiles, boots and works fine here.

NACK. Too late.

Bastian

--
No problem is insoluble.
-- Dr. Janet Wallace, "The Deadly Years", stardate 3479.4


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

* maximilian attems <max@stro.at> [2008-06-09 23:51]:
> planing to switch x86 to it for 2.6.26.
> compiles, boots and works fine here.
>
> please update other archs too for the default Lenny gcc.

IMHO there's too little time to proper test this major change. You
often get obscure bugs when you move the kernel to a new GCC and given
where we are in our release process I'm not sure there's enough time
to find these problems.

If there are no objections, I'll leave arm and mips at gcc 4.1.
--
Martin Michlmayr
http://www.cyrius.com/


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Hi!
On Tue, Jun 10, 2008 at 09:01:59AM +0200, Bastian Blank wrote:
> On Mon, Jun 09, 2008 at 11:51:28PM +0200, maximilian attems wrote:
> > planing to switch x86 to it for 2.6.26.
> > compiles, boots and works fine here.
>
> NACK. Too late.

I'd like to see this for amd64 too, but I guess we are indeed too late.

Are we really releasing with .26?

Best regards
Frederik Schüler

--
ENOSIG