[jira] [Updated] (STDCXX-1071) numpunct facet cache initialization is not thread -safe

2012-09-28 Thread Liviu Nicoara (JIRA)

 [ 
https://issues.apache.org/jira/browse/STDCXX-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Liviu Nicoara updated STDCXX-1071:
--

Attachment: (was: patch-4.3.x.diff)

 numpunct facet cache initialization is not thread -safe
 ---

 Key: STDCXX-1071
 URL: https://issues.apache.org/jira/browse/STDCXX-1071
 Project: C++ Standard Library
  Issue Type: Bug
  Components: 22. Localization, Thread Safety
Affects Versions: 4.2.1, 4.2.x, 4.3.x, 5.0.0
 Environment: $ uname -a; CC -V
 Linux behemoth 2.6.37.6 #3 SMP Sat Apr 9 22:49:32 CDT 2011 x86_64 AMD 
 Opteron(tm) Processor 6134 AuthenticAMD GNU/Linux
 CC: Sun C++ 5.12 Linux_i386 2011/11/16
Reporter: Liviu Nicoara
Priority: Critical
  Labels: DCII, localization, numpunct, thread-safety
 Fix For: 4.2.1, 4.2.x, 4.3.x, 5.0.0

 Attachments: library-reduction.cpp, patch-4.2.x.diff, 
 patch-timings.tgz, punct-mt.cpp

   Original Estimate: 8h
  Remaining Estimate: 8h

 The bug affects the initialization of the cached data in numpunct facet. The 
 failing test is 22.locale.numpunct.cpp in certain builds: Linux with SUNPro 
 5.12, optimized, most likely to fail. It has been reported (see linked 
 incidents) to fail on SPARC as well. It manifests in variate ways: sometimes 
 as heap corruption, sometimes as access violations, etc. Test cases and 
 library reduction programs to follow. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (STDCXX-1071) numpunct facet cache initialization is not thread -safe

2012-09-28 Thread Liviu Nicoara (JIRA)

 [ 
https://issues.apache.org/jira/browse/STDCXX-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Liviu Nicoara updated STDCXX-1071:
--

Attachment: patch-5.0.x.diff

 numpunct facet cache initialization is not thread -safe
 ---

 Key: STDCXX-1071
 URL: https://issues.apache.org/jira/browse/STDCXX-1071
 Project: C++ Standard Library
  Issue Type: Bug
  Components: 22. Localization, Thread Safety
Affects Versions: 4.2.1, 4.2.x, 4.3.x, 5.0.0
 Environment: $ uname -a; CC -V
 Linux behemoth 2.6.37.6 #3 SMP Sat Apr 9 22:49:32 CDT 2011 x86_64 AMD 
 Opteron(tm) Processor 6134 AuthenticAMD GNU/Linux
 CC: Sun C++ 5.12 Linux_i386 2011/11/16
Reporter: Liviu Nicoara
Priority: Critical
  Labels: DCII, localization, numpunct, thread-safety
 Fix For: 4.2.1, 4.2.x, 4.3.x, 5.0.0

 Attachments: library-reduction.cpp, patch-4.2.x.diff, 
 patch-5.0.x.diff, patch-timings.tgz, punct-mt.cpp

   Original Estimate: 8h
  Remaining Estimate: 8h

 The bug affects the initialization of the cached data in numpunct facet. The 
 failing test is 22.locale.numpunct.cpp in certain builds: Linux with SUNPro 
 5.12, optimized, most likely to fail. It has been reported (see linked 
 incidents) to fail on SPARC as well. It manifests in variate ways: sometimes 
 as heap corruption, sometimes as access violations, etc. Test cases and 
 library reduction programs to follow. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (STDCXX-1071) numpunct facet cache initialization is not thread -safe

2012-09-26 Thread Liviu Nicoara (JIRA)

 [ 
https://issues.apache.org/jira/browse/STDCXX-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Liviu Nicoara updated STDCXX-1071:
--

Attachment: library-reduction.cpp

 numpunct facet cache initialization is not thread -safe
 ---

 Key: STDCXX-1071
 URL: https://issues.apache.org/jira/browse/STDCXX-1071
 Project: C++ Standard Library
  Issue Type: Bug
  Components: 22. Localization, Thread Safety
Affects Versions: 4.2.1, 4.2.x, 4.3.x, 5.0.0
 Environment: $ uname -a; CC -V
 Linux behemoth 2.6.37.6 #3 SMP Sat Apr 9 22:49:32 CDT 2011 x86_64 AMD 
 Opteron(tm) Processor 6134 AuthenticAMD GNU/Linux
 CC: Sun C++ 5.12 Linux_i386 2011/11/16
Reporter: Liviu Nicoara
Priority: Critical
  Labels: DCII, localization, numpunct, thread-safety
 Fix For: 4.2.1, 4.2.x, 4.3.x, 5.0.0

 Attachments: library-reduction.cpp

   Original Estimate: 8h
  Remaining Estimate: 8h

 The bug affects the initialization of the cached data in numpunct facet. The 
 failing test is 22.locale.numpunct.cpp in certain builds: Linux with SUNPro 
 5.12, optimized, most likely to fail. It has been reported (see linked 
 incidents) to fail on SPARC as well. It manifests in variate ways: sometimes 
 as heap corruption, sometimes as access violations, etc. Test cases and 
 library reduction programs to follow. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (STDCXX-1071) numpunct facet cache initialization is not thread -safe

2012-09-26 Thread Liviu Nicoara (JIRA)

 [ 
https://issues.apache.org/jira/browse/STDCXX-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Liviu Nicoara updated STDCXX-1071:
--

Attachment: punct-mt.cpp

 numpunct facet cache initialization is not thread -safe
 ---

 Key: STDCXX-1071
 URL: https://issues.apache.org/jira/browse/STDCXX-1071
 Project: C++ Standard Library
  Issue Type: Bug
  Components: 22. Localization, Thread Safety
Affects Versions: 4.2.1, 4.2.x, 4.3.x, 5.0.0
 Environment: $ uname -a; CC -V
 Linux behemoth 2.6.37.6 #3 SMP Sat Apr 9 22:49:32 CDT 2011 x86_64 AMD 
 Opteron(tm) Processor 6134 AuthenticAMD GNU/Linux
 CC: Sun C++ 5.12 Linux_i386 2011/11/16
Reporter: Liviu Nicoara
Priority: Critical
  Labels: DCII, localization, numpunct, thread-safety
 Fix For: 4.2.1, 4.2.x, 4.3.x, 5.0.0

 Attachments: library-reduction.cpp, punct-mt.cpp

   Original Estimate: 8h
  Remaining Estimate: 8h

 The bug affects the initialization of the cached data in numpunct facet. The 
 failing test is 22.locale.numpunct.cpp in certain builds: Linux with SUNPro 
 5.12, optimized, most likely to fail. It has been reported (see linked 
 incidents) to fail on SPARC as well. It manifests in variate ways: sometimes 
 as heap corruption, sometimes as access violations, etc. Test cases and 
 library reduction programs to follow. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


[jira] [Updated] (STDCXX-1071) numpunct facet cache initialization is not thread -safe

2012-09-26 Thread Liviu Nicoara (JIRA)

 [ 
https://issues.apache.org/jira/browse/STDCXX-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Liviu Nicoara updated STDCXX-1071:
--

Attachment: patch-4.3.x.diff
patch-4.2.x.diff

 numpunct facet cache initialization is not thread -safe
 ---

 Key: STDCXX-1071
 URL: https://issues.apache.org/jira/browse/STDCXX-1071
 Project: C++ Standard Library
  Issue Type: Bug
  Components: 22. Localization, Thread Safety
Affects Versions: 4.2.1, 4.2.x, 4.3.x, 5.0.0
 Environment: $ uname -a; CC -V
 Linux behemoth 2.6.37.6 #3 SMP Sat Apr 9 22:49:32 CDT 2011 x86_64 AMD 
 Opteron(tm) Processor 6134 AuthenticAMD GNU/Linux
 CC: Sun C++ 5.12 Linux_i386 2011/11/16
Reporter: Liviu Nicoara
Priority: Critical
  Labels: DCII, localization, numpunct, thread-safety
 Fix For: 4.2.1, 4.2.x, 4.3.x, 5.0.0

 Attachments: library-reduction.cpp, patch-4.2.x.diff, 
 patch-4.3.x.diff, punct-mt.cpp

   Original Estimate: 8h
  Remaining Estimate: 8h

 The bug affects the initialization of the cached data in numpunct facet. The 
 failing test is 22.locale.numpunct.cpp in certain builds: Linux with SUNPro 
 5.12, optimized, most likely to fail. It has been reported (see linked 
 incidents) to fail on SPARC as well. It manifests in variate ways: sometimes 
 as heap corruption, sometimes as access violations, etc. Test cases and 
 library reduction programs to follow. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira