Bug 821251

Summary: New libstdc++ fail on RHEL6.3
Product: Red Hat Enterprise Linux 6 Reporter: Marek Polacek <mpolacek>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED WONTFIX QA Contact: qe-baseos-tools-bugs
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.3CC: law, mnewsome
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-10 14:26:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1023566    

Description Marek Polacek 2012-05-13 14:48:43 UTC
gcc-4.4.6-3 -> gcc-4.4.6-4.

 		=== libstdc++ tests ===
@@ -1642,7 +1642,7 @@
 PASS: 22_locale/num_put/put/char/9.cc (test for excess errors)
 PASS: 22_locale/num_put/put/char/9.cc execution test
 PASS: 22_locale/num_put/put/char/9780-2.cc (test for excess errors)
-FAIL: 22_locale/num_put/put/char/9780-2.cc execution test
+PASS: 22_locale/num_put/put/char/9780-2.cc execution test
 PASS: 22_locale/num_put/put/char/wrapped_env.cc (test for excess errors)
 PASS: 22_locale/num_put/put/char/wrapped_env.cc execution test
 PASS: 22_locale/num_put/put/char/wrapped_locale.cc (test for excess errors)

Very likely not a gcc bug, might be just locales change, similar to Bug 771026,
but filing anyway to keep the record of it.  Happens on all arches.

Comment 2 RHEL Program Management 2012-05-17 04:03:39 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 4 Jakub Jelinek 2014-10-02 14:20:40 UTC
As the testcase changed (with https://gcc.gnu.org/ml/libstdc++/2011-12/msg00091.html ), this isn't really a regression IMHO, it is just testing a different testcase.