Martin Michlmayr <[EMAIL PROTECTED]> writes:
> * Falk Hueffner <[EMAIL PROTECTED]> [2006-03-20 00:20]:
>> I mean 4.2 mainline. I don't know yet whether 4.1 mainline is fixed.
>> I'm pretty sure if it isn't already, it will get fixed.
>
> FWIW, I'd feel more comfortable if you'd explicitly try to m
* Falk Hueffner <[EMAIL PROTECTED]> [2006-03-19 22:44]:
> I can reproduce this with gcc-snapshot, but not with 4.2.0 20060304,
> so it's probably fixed already, at least on mainline.
If you can not reproduce it with 4.2.0, does this mean that a future
version of 4._1_ will contain the fix? Is tha
* Falk Hueffner <[EMAIL PROTECTED]> [2006-03-20 00:20]:
> I mean 4.2 mainline. I don't know yet whether 4.1 mainline is fixed.
> I'm pretty sure if it isn't already, it will get fixed.
FWIW, I'd feel more comfortable if you'd explicitly try to make sure
it gets fixed in 4.1. But I've no idea how
Martin Michlmayr <[EMAIL PROTECTED]> writes:
> * Falk Hueffner <[EMAIL PROTECTED]> [2006-03-19 22:44]:
>> I can reproduce this with gcc-snapshot, but not with 4.2.0 20060304,
>> so it's probably fixed already, at least on mainline.
>
> If you can not reproduce it with 4.2.0, does this mean that a
Hi,
I can reproduce this with gcc-snapshot, but not with 4.2.0 20060304,
so it's probably fixed already, at least on mainline.
--
Falk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
5 matches
Mail list logo
