[Bug 461303] Re: generates-bad-code regression

[Zooko O'Whielacronx]

Could a "project maintainer or bug supervisor" please change the Fedora
bug status from "In Progress" to "Fix Released" or authorize me to do
so?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/461303

Title:
  generates-bad-code regression

Status in binutils:
  Fix Released
Status in MinGW:
  Unknown
Status in Python Crypto Library Based on Crypto++:
  Fix Released
Status in Tahoe, the Lovely Accessible File System:
  Fix Released
Status in “binutils” package in Ubuntu:
  Fix Released
Status in “libcrypto++” package in Ubuntu:
  Invalid
Status in “binutils” source package in Karmic:
  Fix Released
Status in “libcrypto++” source package in Karmic:
  Invalid
Status in “binutils” package in Fedora:
  In Progress

Bug description:
  g++-4.4 4.4.1-3ubuntu3 was used to build libcrypto++8.  The current
  g++-4.4 in Karmic is g++-4.4 4.4.1-4ubuntu8.  When 4.4.1-4ubuntu8 is
  used to build libcrypto++8 then the libcrypto++8 self-tests hang
  during the SHA validation.  It appears that there has been a
  regression between g++ 4.4.1-3ubuntu3 and -4ubuntu8 such that the new
  one generates bad code.

  In addition to the libcrypto++8 self-tests hanging during SHA
  validation, if you then build python-pycryptopp using the libcrypto++8
  lib that was built by g++ 4.4.1-4ubuntu8, then the python-pycryptopp
  library gets segfaults when it runs its self-tests. Here is the
  pycryptopp upstream buildbot showing segfaults on karmic, along with a
  valgrind report:

  http://allmydata.org/buildbot-pycryptopp/waterfall
  http://allmydata.org/buildbot-pycryptopp/builders/linux-amd64-ubuntu-karmic-yukyuk/builds/11/steps/test/logs/valgrind

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/461303/+subscriptions