Red Hat Bugzilla – Bug 463388
[LTC 6.0 FEAT] 201154:LoP Upgrade binutils to 2.18 or higher
Last modified: 2013-03-07 21:04:39 EST
Emily J. Ratliff <firstname.lastname@example.org> - 2008-09-17 17:19 EDT
1. Feature Overview:
Feature Id: 
a. Name of Feature: LoP Upgrade to GCC-4.3 and related packages - binutils
b. Feature Description
GCC-4.3 contains Decimal Floating Point support plus many additional
optimizations useful to POWER. Please update binutils along with the request to
update gcc to the latest level.
2. Feature Details:
Arch Specificity: Both
Affects Toolchain: Yes
Delivery Mechanism: Direct from community
Request Type: Package - Update Version
d. Upstream Acceptance: Accepted
Sponsor Priority 1
f. Severity: High
IBM Confidential: no
Code Contribution: no
g. Component Version Target: GCC-4.3, binutils-2.18, GLIBC-2.7+
Performance Assistance: yes
3. Business Case
Support multiple POWER6/7 features while minimizing backports
Performance improvements for POWER6/7 customers, direct support for POWER6/7
4. Primary contact at Red Hat:
5. Primary contacts at Partner:
Project Management Contact:
Michael Hohnbaum, email@example.com, 503-578-5486
Steve Munroe, firstname.lastname@example.org
The feature requested has already been accepted into the upstream code base
planned for the next major release of Red Hat Enterprise Linux.
When the next milestone release of Red Hat Enterprise Linux 6 is available,
please verify that the feature requested is present and functioning as
RHEL6 will be based on Fedora11 and that will based on binutils 2.19.1, so we are all set here.
Fixed in 'binutils-220.127.116.11.14-34.el6', included in compose 'RHEL6.0-20091028.0'.
Moving to ON_QA.
------- Comment From email@example.com 2009-11-16 13:33 EDT-------
binutils-18.104.22.168.14-34.el6.ppc64 found on RHEL6-20091110.
------- Comment From firstname.lastname@example.org 2010-05-03 12:48 EDT-------
Binutils verified to be v2.20 on RHEL6 Beta 1. Closing.
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.