Matthias Klose dixit:
>I'll propose 4.7.2-4 for testing, so please update.
OK thanks for the heads-up, will do after I get over
the worst of this cold I caught.
>However I couldn't find the upstream GCC issue.
Didn’t report one yet, had too much dayjob-related
stuff to do this week. Will do.
b
On 04.10.2012 18:57, Thorsten Glaser wrote:
> Matthias Klose dixit:
>
>> how does gcc-snapshot behave?
>
> It also introduces this failure.
>
>> If you think it's a regression, please could you forward it upstream?
>
> OK. In the meantime, I’ve prepared workarounds upstream (and
> made the code
Matthias Klose dixit:
>how does gcc-snapshot behave?
It also introduces this failure.
>If you think it's a regression, please could you forward it upstream?
OK. In the meantime, I’ve prepared workarounds upstream (and
made the code a bit less depending on -fwrapv), but I need to
know whether I
On 03.10.2012 15:59, Thorsten Glaser wrote:
> Hi,
>
> https://bugs.launchpad.net/ubuntu/+source/mksh/+bug/1058035
> was just the beginning, as gcc-snapshot in Debian had it (I
> wrote that in the bugreport already), but, now, gcc-4.{6,7}
> in sid also have it.
>
> I’ve just tracked it down for gc
Hi,
https://bugs.launchpad.net/ubuntu/+source/mksh/+bug/1058035
was just the beginning, as gcc-snapshot in Debian had it (I
wrote that in the bugreport already), but, now, gcc-4.{6,7}
in sid also have it.
I’ve just tracked it down for gcc-4.6 to have been introdu‐
ced between 4.6.3-9 and 4.6.3-10
5 matches
Mail list logo
