
| Key: |
STDCXX-839
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Martin Sebor
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Time Tracking:
|
|
Original Estimate:
|
2h
|
|
|
Remaining Estimate:
|
2h
|
|
|
Time Spent:
|
Not Specified
|
|
|
|
|
Environment:
|
Intel C++ 10.0
Red Hat Enterprise Linux Server release 5 (Tikanga)
Intel C++ 10.0
Red Hat Enterprise Linux Server release 5 (Tikanga)
|
|
Issue Links:
|
dependent
|
|
This issue depends upon:
|
|
|
STDCXX-892 [Darwin, Linux] use xlocale for efficiency
|
|
|
|
|
|
|
|
| Regression: |
Regression
|
| Severity: |
Inefficiency
|
During nightly builds the test 22.locale.numpunct.mt.cpp times out on many platforms, including some build types with gcc 4.1 and all build types with Intel C++ 10/Linux, or with XLC++ 9.0 on AIX. The output below shows that it takes nearly 8 minutes to run to completion, which is in contrast to most other .mt tests which typically complete in less than 2 minutes. Since most of the locale thread safety tests follow the same pattern there must be some inefficiency either in the implementation of the std::numpunct facet or in specifics of the test itself (or both).
Since this test is new in 4.2.1, its failure is a regression.
|
|
Description
|
During nightly builds the test 22.locale.numpunct.mt.cpp times out on many platforms, including some build types with gcc 4.1 and all build types with Intel C++ 10/Linux, or with XLC++ 9.0 on AIX. The output below shows that it takes nearly 8 minutes to run to completion, which is in contrast to most other .mt tests which typically complete in less than 2 minutes. Since most of the locale thread safety tests follow the same pattern there must be some inefficiency either in the implementation of the std::numpunct facet or in specifics of the test itself (or both).
Since this test is new in 4.2.1, its failure is a regression.
|
Show » |
| No work has yet been logged on this issue.
|
|