Your message dated Sun, 20 Mar 2011 18:28:38 +0100
with message-id <4d863946.5040...@debian.org>
and subject line Re: Bug#611249: gcc-4.4: please update powerpcspe patches
has caused the Debian Bug report #611249,
regarding gcc-4.4: Fix PR44606 concerning powerpcspe architecture
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
611249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gcc-4.4
Version: 4.4.5-9
Severity: normal
Tags: patch
Hi, the attached .debdiff fixes PR44606 [1], a register-allocation bug
that (seldomly) miscompiles floating point code in the unofficial
powerpcspe port [2].
This is a backport of commit 168347 from GCC svn [3].
The patch modifies debian/rules.patch to only apply the patch on
powerpcspe, so there should be no side-effects on other architectures.
I verified the patch to compile and be effective on a powerpcspe sid
installation running on a P2020RDB development board.
I guess the same patch should go into gcc-4.3 as well, going to post a
corresponding bug report in the next days.
cheers,
David
[1] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44606
[2] http://wiki.debian.org/PowerPCSPEPort
[3] http://gcc.gnu.org/viewcvs?view=revision&revision=168347
--
GnuPG public key: http://user.cs.tu-berlin.de/~dvdkhlng/dk.gpg
Fingerprint: B17A DC95 D293 657B 4205 D016 7DEF 5323 C174 7D40
pr44606.debdiff
Description: Binary data
pgpIxL0OA2IgT.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
On 18.02.2011 22:55, Sebastian Andrzej Siewior wrote:
> * Matthias Klose | 2011-02-18 12:40:55 [+0100]:
>
>>> Sure thing. I attached 4.4, 4.5 will follow tomorrow.
>>
>> ahh, and I forgot to ask about the gcc-4.6 package.
>
> Attaching diff for 4.5 and 4.6.
applied upstream on all branches
--- End Message ---
