too many warnings reported

Most of our builds with trunk are being reported as having thousands of warnings but when I count the warnings by hand there aren't nearly as many of them. For example, grep says there are 132 lines with the word Warning in this file hpux-11.11-pa-acc-32b-3.63-11s-560283-log but the test result

bulletproofing exec output

I did some work on the exec utility recently. One of the enhancements I added was a summary section at the end of the output. It seems that this had the unexpected consequence to the scripts that interpret the output of the utility, namely that the new summary is taken as additional tests,

Re: atomic tests timing out on Windows

Here are a couple of articles from the Intel Knowledge Base that don't appear to come with a restrictive license or even a copyright. The code is Windows-specific but it should be possible to translate it to something understandable to gcc and other compilers (Sun C++ on x86). How to Determine

Re: atomic tests timing out on Windows

Martin Sebor wrote: Here are a couple of articles from the Intel Knowledge Base that don't appear to come with a restrictive license or even a copyright. The code is Windows-specific but it should be possible to translate it to something understandable to gcc and other compilers (Sun C++ on

[VOTE RESULT] ready to greaduate

The vote to propose stdcxx graduation to the Incubator PMC (and, ultimately, the board) passes unanimously with no -1 or 0 votes. The following people voted +1 (listed in alphabetical order): Andrew Black Mark Brown (non-binding) Justin Erenkrantz Amit Jindal Eric Lemings (non-binding)

next steps toward graduation

If I correctly understand the process, the next step is for us to formally propose graduation to the Incubator PMC. Before we do that we need to go through the Graduation Check List and make sure we have no outstanding issues: http://incubator.apache.org/guides/graduation.html#checklist Here's

Re: atomic tests timing out on Windows

William A. Rowe, Jr. wrote: Martin Sebor wrote: Here are a couple of articles from the Intel Knowledge Base that don't appear to come with a restrictive license or even a copyright. The code is Windows-specific but it should be possible to translate it to something understandable to gcc and

[jira] Created: (STDCXX-503) std::ctype not thread safe

std::ctype not thread safe -- Key: STDCXX-503 URL: https://issues.apache.org/jira/browse/STDCXX-503 Project: C++ Standard Library Issue Type: Bug Components: 22. Localization Environment: Intel C++

[jira] Updated: (STDCXX-503) std::ctype not thread safe

[ https://issues.apache.org/jira/browse/STDCXX-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Sebor updated STDCXX-503: Attachment: 22.locale.ctype.mt.html Attached Intel Thread Checker output for the test.

[jira] Updated: (STDCXX-452) std::numpunct not thread safe

[ https://issues.apache.org/jira/browse/STDCXX-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Sebor updated STDCXX-452: Component/s: Thread Safety Added Thread Safety to the list of components affected by this issue.

[jira] Updated: (STDCXX-453) std::moneypunct not thread safe

[ https://issues.apache.org/jira/browse/STDCXX-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Sebor updated STDCXX-453: Component/s: Thread Safety Added Thread Safety to the list of components affected by this issue.

[jira] Updated: (STDCXX-503) std::ctype not thread safe

[ https://issues.apache.org/jira/browse/STDCXX-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Sebor updated STDCXX-503: Component/s: Thread Safety Added Thread Safety to the list of components affected by this issue.

[jira] Updated: (STDCXX-450) std::use_facetstd::num_put() not thread safe

[ https://issues.apache.org/jira/browse/STDCXX-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Sebor updated STDCXX-450: Component/s: Thread Safety Added Thread Safety to the list of components affected by this issue.

Re: next steps toward graduation

Martin Sebor wrote: 1. Preparations. i) Complete (and sign off) tasks documented in the status file. Status file needs to be updated. The page that's up on the site doesn't reflect the most recent changes to the file (see below). The last time I tried to get the site