You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stdcxx.apache.org by Martin Sebor <se...@roguewave.com> on 2007/10/19 03:43:54 UTC
[VOTE] release stdcxx 4.2.0
I created what I'm hoping will be the final stdcxx 4.2.0 release
candidate, stdcxx-4.2.0-rc-6:
http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-6/
along with a tarball containing the sources:
http://people.apache.org/~sebor/stdcxx/stdcxx-incubating-4.2.0.tar.gz
The MD5 sum for the tarball is: f65ea507f7d82688d1cf241bce25dc01
Instructions on unpacking the tarball, configuring the library,
and building it along with the set of examples and tests, are
in the README file contained in the tarball. The file can also
be viewed directly in Subversion:
http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-6/README
The Jira "Release Notes" for 4.2.0 detailing the vast number of
issues resolved in this release can be found here:
http://tinyurl.com/ytzonz
stdcxx 4.2.0 has been tested on the set of platforms listed in
the README. The test results for most of the tested platforms
can be be viewed on the following page:
http://people.apache.org/~sebor/stdcxx/results/
(there are some failures, most of them due to the Rogue Wave test
infrastructure and IT issues; please disregard those).
Please take the tarball for a spin and vote to approve the release
and to request the approval of the Incubator PMC to publish it on
our site.
Everyone is encouraged to vote, including non-committers.
This vote will close in the usual 72 hours.
Re: [VOTE] release stdcxx 4.2.0
Posted by Martin Sebor <se...@roguewave.com>.
Committed thus:
http://svn.apache.org/viewvc?rev=586619&view=rev
and merged as follows:
http://svn.apache.org/viewvc?rev=586620&view=rev
http://svn.apache.org/viewvc?rev=586621&view=rev
Thank you!
Travis Vitek wrote:
> 2007-10-19 Travis Vitek <vi...@roguewave.com>
>
> * README (Index): Update section names and numbers.
> (VisualStudio Directory Structure): Add new section
> describing expected directory structure.
> (VisualStudio Setup Instructions): Remove filename
> extension from the list of supported configuration
> options so that the provided names match the names
> allowed by the configure script.
>
>
>
> Index: README
> ===================================================================
> --- README (revision 585243)
> +++ README (working copy)
> @@ -25,14 +25,14 @@
> Contents ......................................................... 1
> Requirements ..................................................... 2
> Unpacking Instructions ........................................... 3
> - Directory Structure ...............................................4
> - Source Directory Structure ................................... 4.1
> - Library Files ................................................ 4.2
> - Library Utilities ............................................ 4.3
> - Locales ...................................................... 4.4
> - Test Suite Files ............................................. 4.5
> - Examples and Tutorials ....................................... 4.6
> - Build Directory Structure .................................... 4.7
> + Source Directory Structure ....................................... 4
> + Library Files ................................................ 4.1
> + Library Utilities ............................................ 4.2
> + Locales ...................................................... 4.3
> + Test Suite Files ............................................. 4.4
> + Examples and Tutorials ....................................... 4.5
> + Build Directory Structure .................................... 4.6
> + VisualStudio Build Directory Structure ................... 4.6.1
> Library Build Instructions ....................................... 5
> VisualStudio Setup Instructions .............................. 5.1
> Library Installation ............................................. 6
> @@ -335,6 +335,38 @@
> /.depend/*.d dependencies
>
>
> + 4.6.1 VisualStudio Directory Structure
> + ---------------------------------------
> +
> + The directory tree created and partially populated by the configure
> + script, ${TOPDIR}/configure.bat, has the following structure:
> +
> + ${BUILDDIR}/build_${CONFIG}.bat Root build script
> + | /*.{html,...} Temporary files
> + +- ${CONFIG}/${CONFIG}.sln Root solution
> + | /${CONFIG}_ex.sln Examples solution
> + | /${CONFIG}_loc.sln Locales solution
> + | /${CONFIG}_run.sln Run examples/tests solution
> + | /${CONFIG}_tst.sln Tests solution
> + | /${CONFIG}_tstloc.sln Locales tests solution
> + | /${CONFIG}slngen.log Configuration log file
> + +- Projects/*.vcproj Project files
> + | /examples/*.vcproj Examples project files
> + | /locales/*.vcproj Locales project files
> + | /tests/*.vcproj Tests project files
> + | /util/*.vcproj Utilities project files
> + .
> + . ...${BUILDTYPE} directories generated by running build script
> + .
> + +- ${BUILDTYPE}/bin/*.{exe,...} Binaries and temporary files
> + /examples/*.{exe,...} Binaries and temporary files
> + /include/config.h Generated config header
> + /lib/*.{dll,lib,...} Binaries and temporary files
> + /src/*.{obj,...} Temporary files
> + /tests/*.{obj,...} Binaries and temporary files
> + /src/*.{obj,...} Temporary files
> +
> +
> 5 Library Build Instructions
> -----------------------------
>
> @@ -513,19 +545,19 @@
> specified a current directory is assumed.
>
> <config> name (not pathname) of a config file containing
> - compiler options; the available configuration files
> + compiler options; the available configuration options
> are:
> - icc-9.0.config - for Intel C++ 9.0
> - icc-9.1.config - for Intel C++ 9.1
> - icc-10.0.config - for Intel C++ 10.0
> - icc-10.0-x64.config - for Intel C++ 10.0 (x64 platform)
> - msvc-7.0.config - for Microsoft Visual C++ .NET
> - msvc-7.1.config - for Microsoft Visual C++ .NET 2003
> - msvc-8.0.config - for Microsoft Visual C++ .NET 2005
> - msvc-8.0-x64.config - for Microsoft Visual C++ .NET
> - 2005 (x64 platform)
> - msvcex-8.0.config - for Microsoft Visual C++ Express
> - 2005
> + icc-9.0 - for Intel C++ 9.0
> + icc-9.1 - for Intel C++ 9.1
> + icc-10.0 - for Intel C++ 10.0
> + icc-10.0-x64 - for Intel C++ 10.0 (x64 platform)
> + msvc-7.0 - for Microsoft Visual C++ .NET
> + msvc-7.1 - for Microsoft Visual C++ .NET 2003
> + msvc-8.0 - for Microsoft Visual C++ .NET 2005
> + msvc-8.0-x64 - for Microsoft Visual C++ .NET 2005
> + (x64 platform)
> + msvcex-8.0 - for Microsoft Visual C++ Express
> + 2005
>
> The <config> argument is optional. When not
> specified, the suitable config file will be selected
>
>
>> -----Original Message-----
>> From: Travis Vitek [mailto:Travis.Vitek@roguewave.com]
>> Sent: Friday, October 19, 2007 11:19 AM
>> To: stdcxx-dev@incubator.apache.org
>> Subject: RE: [VOTE] release stdcxx 4.2.0
>>
>>
>> Sure.
>>
>>> Martin Sebor wrote:
>>>
>>> Ugh. I thought you had covered all the issues in your patch.
>>> I should have read your post more carefully. Let me work on
>>> sections 4.4, and 6. I could use help with section 4.6, the
>>> Windows build directory structure and Windows installation.
>>> I'm not sure if Farid's still online after pulling an
>>> allnighter last night. If not, Travis, can you give it a try?
>>>
>>> Martin
>>>
RE: [VOTE] release stdcxx 4.2.0
Posted by Travis Vitek <Tr...@roguewave.com>.
2007-10-19 Travis Vitek <vi...@roguewave.com>
* README (Index): Update section names and numbers.
(VisualStudio Directory Structure): Add new section
describing expected directory structure.
(VisualStudio Setup Instructions): Remove filename
extension from the list of supported configuration
options so that the provided names match the names
allowed by the configure script.
Index: README
===================================================================
--- README (revision 585243)
+++ README (working copy)
@@ -25,14 +25,14 @@
Contents ......................................................... 1
Requirements ..................................................... 2
Unpacking Instructions ........................................... 3
- Directory Structure ...............................................4
- Source Directory Structure ................................... 4.1
- Library Files ................................................ 4.2
- Library Utilities ............................................ 4.3
- Locales ...................................................... 4.4
- Test Suite Files ............................................. 4.5
- Examples and Tutorials ....................................... 4.6
- Build Directory Structure .................................... 4.7
+ Source Directory Structure ....................................... 4
+ Library Files ................................................ 4.1
+ Library Utilities ............................................ 4.2
+ Locales ...................................................... 4.3
+ Test Suite Files ............................................. 4.4
+ Examples and Tutorials ....................................... 4.5
+ Build Directory Structure .................................... 4.6
+ VisualStudio Build Directory Structure ................... 4.6.1
Library Build Instructions ....................................... 5
VisualStudio Setup Instructions .............................. 5.1
Library Installation ............................................. 6
@@ -335,6 +335,38 @@
/.depend/*.d dependencies
+ 4.6.1 VisualStudio Directory Structure
+ ---------------------------------------
+
+ The directory tree created and partially populated by the configure
+ script, ${TOPDIR}/configure.bat, has the following structure:
+
+ ${BUILDDIR}/build_${CONFIG}.bat Root build script
+ | /*.{html,...} Temporary files
+ +- ${CONFIG}/${CONFIG}.sln Root solution
+ | /${CONFIG}_ex.sln Examples solution
+ | /${CONFIG}_loc.sln Locales solution
+ | /${CONFIG}_run.sln Run examples/tests solution
+ | /${CONFIG}_tst.sln Tests solution
+ | /${CONFIG}_tstloc.sln Locales tests solution
+ | /${CONFIG}slngen.log Configuration log file
+ +- Projects/*.vcproj Project files
+ | /examples/*.vcproj Examples project files
+ | /locales/*.vcproj Locales project files
+ | /tests/*.vcproj Tests project files
+ | /util/*.vcproj Utilities project files
+ .
+ . ...${BUILDTYPE} directories generated by running build script
+ .
+ +- ${BUILDTYPE}/bin/*.{exe,...} Binaries and temporary files
+ /examples/*.{exe,...} Binaries and temporary files
+ /include/config.h Generated config header
+ /lib/*.{dll,lib,...} Binaries and temporary files
+ /src/*.{obj,...} Temporary files
+ /tests/*.{obj,...} Binaries and temporary files
+ /src/*.{obj,...} Temporary files
+
+
5 Library Build Instructions
-----------------------------
@@ -513,19 +545,19 @@
specified a current directory is assumed.
<config> name (not pathname) of a config file containing
- compiler options; the available configuration files
+ compiler options; the available configuration options
are:
- icc-9.0.config - for Intel C++ 9.0
- icc-9.1.config - for Intel C++ 9.1
- icc-10.0.config - for Intel C++ 10.0
- icc-10.0-x64.config - for Intel C++ 10.0 (x64 platform)
- msvc-7.0.config - for Microsoft Visual C++ .NET
- msvc-7.1.config - for Microsoft Visual C++ .NET 2003
- msvc-8.0.config - for Microsoft Visual C++ .NET 2005
- msvc-8.0-x64.config - for Microsoft Visual C++ .NET
- 2005 (x64 platform)
- msvcex-8.0.config - for Microsoft Visual C++ Express
- 2005
+ icc-9.0 - for Intel C++ 9.0
+ icc-9.1 - for Intel C++ 9.1
+ icc-10.0 - for Intel C++ 10.0
+ icc-10.0-x64 - for Intel C++ 10.0 (x64 platform)
+ msvc-7.0 - for Microsoft Visual C++ .NET
+ msvc-7.1 - for Microsoft Visual C++ .NET 2003
+ msvc-8.0 - for Microsoft Visual C++ .NET 2005
+ msvc-8.0-x64 - for Microsoft Visual C++ .NET 2005
+ (x64 platform)
+ msvcex-8.0 - for Microsoft Visual C++ Express
+ 2005
The <config> argument is optional. When not
specified, the suitable config file will be selected
>-----Original Message-----
>From: Travis Vitek [mailto:Travis.Vitek@roguewave.com]
>Sent: Friday, October 19, 2007 11:19 AM
>To: stdcxx-dev@incubator.apache.org
>Subject: RE: [VOTE] release stdcxx 4.2.0
>
>
>Sure.
>
>>Martin Sebor wrote:
>>
>>Ugh. I thought you had covered all the issues in your patch.
>>I should have read your post more carefully. Let me work on
>>sections 4.4, and 6. I could use help with section 4.6, the
>>Windows build directory structure and Windows installation.
>>I'm not sure if Farid's still online after pulling an
>>allnighter last night. If not, Travis, can you give it a try?
>>
>>Martin
>>
>
RE: [VOTE] release stdcxx 4.2.0
Posted by Travis Vitek <Tr...@roguewave.com>.
Sure.
>Martin Sebor wrote:
>
>Ugh. I thought you had covered all the issues in your patch.
>I should have read your post more carefully. Let me work on
>sections 4.4, and 6. I could use help with section 4.6, the
>Windows build directory structure and Windows installation.
>I'm not sure if Farid's still online after pulling an
>allnighter last night. If not, Travis, can you give it a try?
>
>Martin
>
Re: [VOTE] release stdcxx 4.2.0
Posted by Martin Sebor <se...@roguewave.com>.
Andrew Black wrote:
> My concern about using -rc-6 as the 4.2.0 release is that there are
> still several flaws in the readme file that have yet to be addressed.
> See my note in
> http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200710.mbox/%3c4715163A.6000908@roguewave.com%3e
> providing a list of these discrepancies. I provided a patch for the
> issues in section 10 (which need to be propagated to the website), but I
> am busy with other projects at work, and don't have time to work on the
> section 4 and 6 issues I noted.
Ugh. I thought you had covered all the issues in your patch.
I should have read your post more carefully. Let me work on
sections 4.4, and 6. I could use help with section 4.6, the
Windows build directory structure and Windows installation.
I'm not sure if Farid's still online after pulling an
allnighter last night. If not, Travis, can you give it a try?
Martin
>
> --Andrew Black
>
> Martin Sebor wrote:
>> I created what I'm hoping will be the final stdcxx 4.2.0 release
>> candidate, stdcxx-4.2.0-rc-6:
>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-6/
>>
>> along with a tarball containing the sources:
>> http://people.apache.org/~sebor/stdcxx/stdcxx-incubating-4.2.0.tar.gz
>>
>> The MD5 sum for the tarball is: f65ea507f7d82688d1cf241bce25dc01
>>
>> Instructions on unpacking the tarball, configuring the library,
>> and building it along with the set of examples and tests, are
>> in the README file contained in the tarball. The file can also
>> be viewed directly in Subversion:
>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-6/README
>>
>> The Jira "Release Notes" for 4.2.0 detailing the vast number of
>> issues resolved in this release can be found here:
>> http://tinyurl.com/ytzonz
>>
>> stdcxx 4.2.0 has been tested on the set of platforms listed in
>> the README. The test results for most of the tested platforms
>> can be be viewed on the following page:
>> http://people.apache.org/~sebor/stdcxx/results/
>> (there are some failures, most of them due to the Rogue Wave test
>> infrastructure and IT issues; please disregard those).
>>
>> Please take the tarball for a spin and vote to approve the release
>> and to request the approval of the Incubator PMC to publish it on
>> our site.
>>
>> Everyone is encouraged to vote, including non-committers.
>>
>> This vote will close in the usual 72 hours.
Re: [VOTE] release stdcxx 4.2.0
Posted by Andrew Black <ab...@roguewave.com>.
My concern about using -rc-6 as the 4.2.0 release is that there are
still several flaws in the readme file that have yet to be addressed.
See my note in
http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200710.mbox/%3c4715163A.6000908@roguewave.com%3e
providing a list of these discrepancies. I provided a patch for the
issues in section 10 (which need to be propagated to the website), but I
am busy with other projects at work, and don't have time to work on the
section 4 and 6 issues I noted.
--Andrew Black
Martin Sebor wrote:
> I created what I'm hoping will be the final stdcxx 4.2.0 release
> candidate, stdcxx-4.2.0-rc-6:
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-6/
>
> along with a tarball containing the sources:
> http://people.apache.org/~sebor/stdcxx/stdcxx-incubating-4.2.0.tar.gz
>
> The MD5 sum for the tarball is: f65ea507f7d82688d1cf241bce25dc01
>
> Instructions on unpacking the tarball, configuring the library,
> and building it along with the set of examples and tests, are
> in the README file contained in the tarball. The file can also
> be viewed directly in Subversion:
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-6/README
>
> The Jira "Release Notes" for 4.2.0 detailing the vast number of
> issues resolved in this release can be found here:
> http://tinyurl.com/ytzonz
>
> stdcxx 4.2.0 has been tested on the set of platforms listed in
> the README. The test results for most of the tested platforms
> can be be viewed on the following page:
> http://people.apache.org/~sebor/stdcxx/results/
> (there are some failures, most of them due to the Rogue Wave test
> infrastructure and IT issues; please disregard those).
>
> Please take the tarball for a spin and vote to approve the release
> and to request the approval of the Incubator PMC to publish it on
> our site.
>
> Everyone is encouraged to vote, including non-committers.
>
> This vote will close in the usual 72 hours.
Re: [VOTE] release stdcxx 4.2.0 (candidate 7)
Posted by Andrew Black <ab...@roguewave.com>.
Martin Sebor wrote:
> Andrew Black wrote:
>> I reviewed the README again, and I'm seeing a few nits, but I don't
>> think they're worth holding the release up for (someone else may
>> disagree).
>>
>> I feel the first paragraph of section 4.4 has a poorly worded or
>> inaccurate description of where the rwtest library lives.
>
> I'm not sure I see what you mean. Can you be more specific?
The wording in question is (in part) "... the test driver library,
rwtest, in ${TOPDIR}/tests/include/, ...". I believe the words "a set
of headers" were deleted by mistake in r586592. Adding these words back
in would make the quote read "... the test driver library, rwtest, a set
of headers, in ${TOPDIR}/tests/include/, ...". I wondered if it would
make sense to note where the rwtest library lives in this first
paragraph, but I think resolving this wording (as noted above) would
resolve my concerns.
--Andrew Black
Re: [VOTE] release stdcxx 4.2.0 (candidate 7)
Posted by Martin Sebor <se...@roguewave.com>.
Andrew Black wrote:
> I reviewed the README again, and I'm seeing a few nits, but I don't
> think they're worth holding the release up for (someone else may disagree).
>
> I feel the first paragraph of section 4.4 has a poorly worded or
> inaccurate description of where the rwtest library lives.
I'm not sure I see what you mean. Can you be more specific?
> I also wonder
> if the test harness needs to be better described, as it's referenced in
> several places, but not talked much about.
It probably should be. At the very least, we should document how
to run the tests. Usually, in other open source projects, it's
done by typing make test or make check. I don't think we support
either (I think we expect make run or some such).
>
> In section 5, it is claimed that the BUILDDIR argument is required, but
> this actually isn't the case, as the value will default to
> ${TOPDIR}/build .
Correct. Let me fix that.
> In section 5.1, no reference is made to the msvc-9.0
> and msvc-9.0-x64 config options.
Let me add them.
>
> Section 7 still references the old runall.sh script in the final
> paragraph, which may need to be rewritten. The paragraph before that
> includes some 'best results' instructions, which also were related to
> the old runall.sh script.
I took it out.
Check out the changes here and let me know if you see anything
else that needs fixing:
http://svn.apache.org/viewvc?rev=587993&view=rev
>
> As far as test builds are concerned, I ran a couple tests. Both builds
> were 11d. The first was on my local machine (OpenSUSE 10.2 -
> 2.6.18.8-0.5-xenpae, gcc version 4.1.2 20061115 (prerelease) (SUSE Linux))
> On this host, 27.stringbuf.xsputn.stdcxx-515.cpp test fails to compile.
> This seems consistent with Redhat 5
Yep, I see it in our build logs. I created a Jira for it:
https://issues.apache.org/jira/browse/STDCXX-614
(though without the failure to
> compile 22.locale.codecvt.out).
Interesting. I see the same result in our nightly builds on this
platform as everywhere else, so it looks like the error is somehow
specific to the way we build the tests in an automated way.
>
> Test suite summary is as follows:
>> PROGRAM SUMMARY:
>> Programs: 187
>> Non-zero exit status: 0
>> Signalled: 11
>> Compiler warnings: 0
>> Linker warnings: 0
>> Runtime warnings: 68
>> Assertions: 11971783
>> Failed assertions: 5341
>
> The second build was on HPUX 11.23, using HPaCC 3.73. On this host, the
> 2.smartptr.shared.cpp, 20.auto.ptr.cpp, and
> regress/27.stringbuf.xsputn.stdcxx-515.cpp tests failed to compile,
> consistent with nightly testing.
I filed the following two issues for these:
https://issues.apache.org/jira/browse/STDCXX-615
https://issues.apache.org/jira/browse/STDCXX-616
Martin
>
> Test suite summary is as follows:
>> PROGRAM SUMMARY:
>> Programs: 187
>> Non-zero exit status: 1
>> Signalled: 8
>> Compiler warnings: 0
>> Linker warnings: 0
>> Runtime warnings: 222
>> Assertions: 11528233
>> Failed assertions: 4706
>
> My vote on rc-7 is +1, despite the issues with the README.
>
> --Andrew Black
>
> Martin Sebor wrote:
>> I just created the next stdcxx 4.2.0 release candidate tag,
>> stdcxx-4.2.0-rc-7, that incorporates changes addressing issues
>> pointed out in the original vote thread.
>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/
>>
>> The tarball containing the release candidate sources can be
>> downloaded from my home directory at the following link:
>> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/stdcxx-incubating-4.2.0.tar.gz
>>
>>
>> The MD5 sum for the tarball is: b43adeb0c72cf4747301818f4dff4fa1
>>
>> Instructions on unpacking the tarball, configuring and building
>> the library and the set of examples and tests, are in the README
>> file contained in the tarball and can also be viewed directly
>> in Subversion:
>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/README
>>
>> The Jira "Release Notes" for 4.2.0 detailing the issues resolved
>> in this release can be viewed here:
>> http://tinyurl.com/ytzonz
>>
>> stdcxx 4.2.0 has been tested on the set of platforms listed in
>> the README. The test results for most of the tested platforms
>> can be be viewed on the following page:
>> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/results/
>> (there are a few failures, most of them attributable to issues in
>> the Rogue Wave test infrastructure; a small number of failures are
>> due to known stdcxx issues).
>>
>> Please download and test the tarball and vote to approve the
>> release and to request the approval of the Incubator PMC to publish
>> it on the stdcxx site. In your vote, please include the names and
>> versions of the compilers and operating systems that you tested on.
>>
>> As always, everyone is encouraged to vote, including non-committers.
>>
>> This vote will close in the usual 72 hours from now, i.e., on
>> Tuesday, 10/23 at 5:00 PM US/Mountain time. Follow the link
>> below for the countdown:
>> http://tinyurl.com/2h5f73
>>
Re: [VOTE] release stdcxx 4.2.0 (candidate 7)
Posted by Andrew Black <ab...@roguewave.com>.
I reviewed the README again, and I'm seeing a few nits, but I don't
think they're worth holding the release up for (someone else may disagree).
I feel the first paragraph of section 4.4 has a poorly worded or
inaccurate description of where the rwtest library lives. I also wonder
if the test harness needs to be better described, as it's referenced in
several places, but not talked much about.
In section 5, it is claimed that the BUILDDIR argument is required, but
this actually isn't the case, as the value will default to
${TOPDIR}/build . In section 5.1, no reference is made to the msvc-9.0
and msvc-9.0-x64 config options.
Section 7 still references the old runall.sh script in the final
paragraph, which may need to be rewritten. The paragraph before that
includes some 'best results' instructions, which also were related to
the old runall.sh script.
As far as test builds are concerned, I ran a couple tests. Both builds
were 11d. The first was on my local machine (OpenSUSE 10.2 -
2.6.18.8-0.5-xenpae, gcc version 4.1.2 20061115 (prerelease) (SUSE Linux))
On this host, 27.stringbuf.xsputn.stdcxx-515.cpp test fails to compile.
This seems consistent with Redhat 5 (though without the failure to
compile 22.locale.codecvt.out).
Test suite summary is as follows:
> PROGRAM SUMMARY:
> Programs: 187
> Non-zero exit status: 0
> Signalled: 11
> Compiler warnings: 0
> Linker warnings: 0
> Runtime warnings: 68
> Assertions: 11971783
> Failed assertions: 5341
The second build was on HPUX 11.23, using HPaCC 3.73. On this host, the
2.smartptr.shared.cpp, 20.auto.ptr.cpp, and
regress/27.stringbuf.xsputn.stdcxx-515.cpp tests failed to compile,
consistent with nightly testing.
Test suite summary is as follows:
> PROGRAM SUMMARY:
> Programs: 187
> Non-zero exit status: 1
> Signalled: 8
> Compiler warnings: 0
> Linker warnings: 0
> Runtime warnings: 222
> Assertions: 11528233
> Failed assertions: 4706
My vote on rc-7 is +1, despite the issues with the README.
--Andrew Black
Martin Sebor wrote:
> I just created the next stdcxx 4.2.0 release candidate tag,
> stdcxx-4.2.0-rc-7, that incorporates changes addressing issues
> pointed out in the original vote thread.
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/
>
> The tarball containing the release candidate sources can be
> downloaded from my home directory at the following link:
> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/stdcxx-incubating-4.2.0.tar.gz
>
>
> The MD5 sum for the tarball is: b43adeb0c72cf4747301818f4dff4fa1
>
> Instructions on unpacking the tarball, configuring and building
> the library and the set of examples and tests, are in the README
> file contained in the tarball and can also be viewed directly
> in Subversion:
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/README
>
> The Jira "Release Notes" for 4.2.0 detailing the issues resolved
> in this release can be viewed here:
> http://tinyurl.com/ytzonz
>
> stdcxx 4.2.0 has been tested on the set of platforms listed in
> the README. The test results for most of the tested platforms
> can be be viewed on the following page:
> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/results/
> (there are a few failures, most of them attributable to issues in
> the Rogue Wave test infrastructure; a small number of failures are
> due to known stdcxx issues).
>
> Please download and test the tarball and vote to approve the
> release and to request the approval of the Incubator PMC to publish
> it on the stdcxx site. In your vote, please include the names and
> versions of the compilers and operating systems that you tested on.
>
> As always, everyone is encouraged to vote, including non-committers.
>
> This vote will close in the usual 72 hours from now, i.e., on
> Tuesday, 10/23 at 5:00 PM US/Mountain time. Follow the link
> below for the countdown:
> http://tinyurl.com/2h5f73
>
error in 26.valarray.transcend.stdcxx-315.cpp (was: Re: [VOTE] release
stdcxx 4.2.0 (candidate 7))
Posted by Martin Sebor <se...@roguewave.com>.
Mark Brown wrote:
> Other than some warnings gcc 4.1.2 on Linux worked fine this time.
> I tried Intel 10.0 and found another test that gave a compiler error.
> I didn't investigate it in great detail but it looks like a problem
> in the test rather than a compiler bug. In any event, I don't see it
> as a blocker for the release and change my vote to +1. Hopefully we
> can fix it in 4.2.1.
I created STDCXX-617 for this:
https://issues.apache.org/jira/browse/STDCXX-617
Martin
>
> /home/mbrown/stdcxx-4.2.0/tests/regress/26.valarray.transcend.stdcxx-315.cpp(43):
> error: implicitly generated assignment operator cannot copy:
> const member "S::self"
> struct S {
> ^
> detected during:
> implicit generation of "S &S::operator=(const S &)" at line
> 1033 of "/home/mbrown/stdcxx-4.2.0/include/valarray"
> instantiation of "std::valarray<_TypeT> std::abs(const
> std::valarray<_TypeT> &) [with _TypeT=S]" at line 78
>
> --Mark
>
> Martin Sebor wrote:
>> I just created the next stdcxx 4.2.0 release candidate tag,
>> stdcxx-4.2.0-rc-7, that incorporates changes addressing issues
>> pointed out in the original vote thread.
>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/
>>
>> The tarball containing the release candidate sources can be
>> downloaded from my home directory at the following link:
>> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/stdcxx-incubating-4.2.0.tar.gz
>>
>>
>> The MD5 sum for the tarball is: b43adeb0c72cf4747301818f4dff4fa1
>>
>> Instructions on unpacking the tarball, configuring and building
>> the library and the set of examples and tests, are in the README
>> file contained in the tarball and can also be viewed directly
>> in Subversion:
>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/README
>>
>> The Jira "Release Notes" for 4.2.0 detailing the issues resolved
>> in this release can be viewed here:
>> http://tinyurl.com/ytzonz
>>
>> stdcxx 4.2.0 has been tested on the set of platforms listed in
>> the README. The test results for most of the tested platforms
>> can be be viewed on the following page:
>> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/results/
>> (there are a few failures, most of them attributable to issues in
>> the Rogue Wave test infrastructure; a small number of failures are
>> due to known stdcxx issues).
>>
>> Please download and test the tarball and vote to approve the
>> release and to request the approval of the Incubator PMC to publish
>> it on the stdcxx site. In your vote, please include the names and
>> versions of the compilers and operating systems that you tested on.
>>
>> As always, everyone is encouraged to vote, including non-committers.
>>
>> This vote will close in the usual 72 hours from now, i.e., on
>> Tuesday, 10/23 at 5:00 PM US/Mountain time. Follow the link
>> below for the countdown:
>> http://tinyurl.com/2h5f73
>>
>>
>
Re: [VOTE] release stdcxx 4.2.0 (candidate 7)
Posted by Mark Brown <ma...@gmail.com>.
Other than some warnings gcc 4.1.2 on Linux worked fine this time.
I tried Intel 10.0 and found another test that gave a compiler error.
I didn't investigate it in great detail but it looks like a problem
in the test rather than a compiler bug. In any event, I don't see it
as a blocker for the release and change my vote to +1. Hopefully we
can fix it in 4.2.1.
/home/mbrown/stdcxx-4.2.0/tests/regress/26.valarray.transcend.stdcxx-315.cpp(43):
error: implicitly generated assignment operator cannot copy:
const member "S::self"
struct S {
^
detected during:
implicit generation of "S &S::operator=(const S &)" at line
1033 of "/home/mbrown/stdcxx-4.2.0/include/valarray"
instantiation of "std::valarray<_TypeT> std::abs(const
std::valarray<_TypeT> &) [with _TypeT=S]" at line 78
--Mark
Martin Sebor wrote:
> I just created the next stdcxx 4.2.0 release candidate tag,
> stdcxx-4.2.0-rc-7, that incorporates changes addressing issues
> pointed out in the original vote thread.
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/
>
> The tarball containing the release candidate sources can be
> downloaded from my home directory at the following link:
> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/stdcxx-incubating-4.2.0.tar.gz
>
>
> The MD5 sum for the tarball is: b43adeb0c72cf4747301818f4dff4fa1
>
> Instructions on unpacking the tarball, configuring and building
> the library and the set of examples and tests, are in the README
> file contained in the tarball and can also be viewed directly
> in Subversion:
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/README
>
> The Jira "Release Notes" for 4.2.0 detailing the issues resolved
> in this release can be viewed here:
> http://tinyurl.com/ytzonz
>
> stdcxx 4.2.0 has been tested on the set of platforms listed in
> the README. The test results for most of the tested platforms
> can be be viewed on the following page:
> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/results/
> (there are a few failures, most of them attributable to issues in
> the Rogue Wave test infrastructure; a small number of failures are
> due to known stdcxx issues).
>
> Please download and test the tarball and vote to approve the
> release and to request the approval of the Incubator PMC to publish
> it on the stdcxx site. In your vote, please include the names and
> versions of the compilers and operating systems that you tested on.
>
> As always, everyone is encouraged to vote, including non-committers.
>
> This vote will close in the usual 72 hours from now, i.e., on
> Tuesday, 10/23 at 5:00 PM US/Mountain time. Follow the link
> below for the countdown:
> http://tinyurl.com/2h5f73
>
>
Re: [VOTE] release stdcxx 4.2.0 (candidate 7)
Posted by Martin Sebor <se...@roguewave.com>.
Tested with gcc 4.1.1 on Fedora Core 6 (no BUILDTYPE or BUILDMODE
just for kicks). Except for a few warnings during compilation there were no
(unexpected) problems or surprises.
+1.
As reminder, the vote closes at 5PM today (http://tinyurl.com/2h5f73).
It would be nice to get a few more votes in.
Martin Sebor wrote:
>
> I just created the next stdcxx 4.2.0 release candidate tag,
> stdcxx-4.2.0-rc-7, that incorporates changes addressing issues
> pointed out in the original vote thread.
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/
>
> The tarball containing the release candidate sources can be
> downloaded from my home directory at the following link:
> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/stdcxx-incubating-4.2.0.tar.gz
>
> The MD5 sum for the tarball is: b43adeb0c72cf4747301818f4dff4fa1
>
> Instructions on unpacking the tarball, configuring and building
> the library and the set of examples and tests, are in the README
> file contained in the tarball and can also be viewed directly
> in Subversion:
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/README
>
> The Jira "Release Notes" for 4.2.0 detailing the issues resolved
> in this release can be viewed here:
> http://tinyurl.com/ytzonz
>
> stdcxx 4.2.0 has been tested on the set of platforms listed in
> the README. The test results for most of the tested platforms
> can be be viewed on the following page:
> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/results/
> (there are a few failures, most of them attributable to issues in
> the Rogue Wave test infrastructure; a small number of failures are
> due to known stdcxx issues).
>
> Please download and test the tarball and vote to approve the
> release and to request the approval of the Incubator PMC to publish
> it on the stdcxx site. In your vote, please include the names and
> versions of the compilers and operating systems that you tested on.
>
> As always, everyone is encouraged to vote, including non-committers.
>
> This vote will close in the usual 72 hours from now, i.e., on
> Tuesday, 10/23 at 5:00 PM US/Mountain time. Follow the link
> below for the countdown:
> http://tinyurl.com/2h5f73
>
>
>
--
View this message in context: http://www.nabble.com/-VOTE--release-stdcxx-4.2.0-tf4650691.html#a13370687
Sent from the stdcxx-dev mailing list archive at Nabble.com.
Re: [VOTE] release stdcxx 4.2.0 (candidate 7)
Posted by Martin Sebor <se...@roguewave.com>.
Liviu Nicoara wrote:
> Martin Sebor wrote:
>> Liviu Nicoara wrote:
>>> +1.
>>
>> Thanks!
>>
>> Just for the record, what particular platform (compiler/OS) and
>> configuration did you test the tarball on?
>
> Slack 10.1, gcc 4.2.0, 11s. I've got:
>
> PROGRAM SUMMARY:
> Programs: 187
> Non-zero exit status: 0
> Signalled: 10
> Compiler warnings: 0
> Linker warnings: 0
> Runtime warnings: 68
> Assertions: 11525052
> Failed assertions: 5229
Thanks. I'm guessing this is the summary for the tests (our nightly
builds show 360 tests but that includes 173 tests that haven't been
moved out of the Rogue Wave Perforce repository and into Apache
Subversion).
The closest we have to gcc 4.2.0 (on Slackware) is probably gcc
4.1.0 (on SuSE 10.0). The test summary for an 11s build is below
(see the full log here: http://tinyurl.com/2yk5z3). There are 12
tests that fail with a signal (9 with ARBRT, 2 with HUP, and 1
with SEGV). As I just said to Brad, we're comfortable with these
results for 4.2.0 (although we should try to reduce the number of
signaled tests in the future).
PROGRAM SUMMARY:
Programs: 360
Non-zero exit status: 1
Signalled: 12
Compiler warnings: 0
Linker warnings: 0
Runtime warnings: 92
Assertions: 13904014
Failed assertions: 6366
Martin
>
> Liviu
>
>>
>> Martin
>>
>>>
>>> Martin Sebor wrote:
>>>> I just created the next stdcxx 4.2.0 release candidate tag,
>>>> stdcxx-4.2.0-rc-7, that incorporates changes addressing issues
>>>> pointed out in the original vote thread.
>>>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/
>>>>
>>>> The tarball containing the release candidate sources can be
>>>> downloaded from my home directory at the following link:
>>>> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/stdcxx-incubating-4.2.0.tar.gz
>>>>
>>>>
>>>> The MD5 sum for the tarball is: b43adeb0c72cf4747301818f4dff4fa1
>>>>
>>>> Instructions on unpacking the tarball, configuring and building
>>>> the library and the set of examples and tests, are in the README
>>>> file contained in the tarball and can also be viewed directly
>>>> in Subversion:
>>>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/README
>>>>
>>>> The Jira "Release Notes" for 4.2.0 detailing the issues resolved
>>>> in this release can be viewed here:
>>>> http://tinyurl.com/ytzonz
>>>>
>>>> stdcxx 4.2.0 has been tested on the set of platforms listed in
>>>> the README. The test results for most of the tested platforms
>>>> can be be viewed on the following page:
>>>> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/results/
>>>> (there are a few failures, most of them attributable to issues in
>>>> the Rogue Wave test infrastructure; a small number of failures are
>>>> due to known stdcxx issues).
>>>>
>>>> Please download and test the tarball and vote to approve the
>>>> release and to request the approval of the Incubator PMC to publish
>>>> it on the stdcxx site. In your vote, please include the names and
>>>> versions of the compilers and operating systems that you tested on.
>>>>
>>>> As always, everyone is encouraged to vote, including non-committers.
>>>>
>>>> This vote will close in the usual 72 hours from now, i.e., on
>>>> Tuesday, 10/23 at 5:00 PM US/Mountain time. Follow the link
>>>> below for the countdown:
>>>> http://tinyurl.com/2h5f73
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: [VOTE] release stdcxx 4.2.0 (candidate 7)
Posted by Liviu Nicoara <li...@roguewave.com>.
Martin Sebor wrote:
> Liviu Nicoara wrote:
>> +1.
>
> Thanks!
>
> Just for the record, what particular platform (compiler/OS) and
> configuration did you test the tarball on?
Slack 10.1, gcc 4.2.0, 11s. I've got:
PROGRAM SUMMARY:
Programs: 187
Non-zero exit status: 0
Signalled: 10
Compiler warnings: 0
Linker warnings: 0
Runtime warnings: 68
Assertions: 11525052
Failed assertions: 5229
Liviu
>
> Martin
>
>>
>> Martin Sebor wrote:
>>> I just created the next stdcxx 4.2.0 release candidate tag,
>>> stdcxx-4.2.0-rc-7, that incorporates changes addressing issues
>>> pointed out in the original vote thread.
>>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/
>>>
>>> The tarball containing the release candidate sources can be
>>> downloaded from my home directory at the following link:
>>> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/stdcxx-incubating-4.2.0.tar.gz
>>>
>>>
>>> The MD5 sum for the tarball is: b43adeb0c72cf4747301818f4dff4fa1
>>>
>>> Instructions on unpacking the tarball, configuring and building
>>> the library and the set of examples and tests, are in the README
>>> file contained in the tarball and can also be viewed directly
>>> in Subversion:
>>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/README
>>>
>>> The Jira "Release Notes" for 4.2.0 detailing the issues resolved
>>> in this release can be viewed here:
>>> http://tinyurl.com/ytzonz
>>>
>>> stdcxx 4.2.0 has been tested on the set of platforms listed in
>>> the README. The test results for most of the tested platforms
>>> can be be viewed on the following page:
>>> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/results/
>>> (there are a few failures, most of them attributable to issues in
>>> the Rogue Wave test infrastructure; a small number of failures are
>>> due to known stdcxx issues).
>>>
>>> Please download and test the tarball and vote to approve the
>>> release and to request the approval of the Incubator PMC to publish
>>> it on the stdcxx site. In your vote, please include the names and
>>> versions of the compilers and operating systems that you tested on.
>>>
>>> As always, everyone is encouraged to vote, including non-committers.
>>>
>>> This vote will close in the usual 72 hours from now, i.e., on
>>> Tuesday, 10/23 at 5:00 PM US/Mountain time. Follow the link
>>> below for the countdown:
>>> http://tinyurl.com/2h5f73
>>>
>>>
>>
>>
>
>
--
Your fault - core dumped.
Re: [VOTE] release stdcxx 4.2.0 (candidate 7)
Posted by Martin Sebor <se...@roguewave.com>.
Liviu Nicoara wrote:
> +1.
Thanks!
Just for the record, what particular platform (compiler/OS) and
configuration did you test the tarball on?
Martin
>
> Martin Sebor wrote:
>> I just created the next stdcxx 4.2.0 release candidate tag,
>> stdcxx-4.2.0-rc-7, that incorporates changes addressing issues
>> pointed out in the original vote thread.
>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/
>>
>> The tarball containing the release candidate sources can be
>> downloaded from my home directory at the following link:
>> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/stdcxx-incubating-4.2.0.tar.gz
>>
>>
>> The MD5 sum for the tarball is: b43adeb0c72cf4747301818f4dff4fa1
>>
>> Instructions on unpacking the tarball, configuring and building
>> the library and the set of examples and tests, are in the README
>> file contained in the tarball and can also be viewed directly
>> in Subversion:
>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/README
>>
>> The Jira "Release Notes" for 4.2.0 detailing the issues resolved
>> in this release can be viewed here:
>> http://tinyurl.com/ytzonz
>>
>> stdcxx 4.2.0 has been tested on the set of platforms listed in
>> the README. The test results for most of the tested platforms
>> can be be viewed on the following page:
>> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/results/
>> (there are a few failures, most of them attributable to issues in
>> the Rogue Wave test infrastructure; a small number of failures are
>> due to known stdcxx issues).
>>
>> Please download and test the tarball and vote to approve the
>> release and to request the approval of the Incubator PMC to publish
>> it on the stdcxx site. In your vote, please include the names and
>> versions of the compilers and operating systems that you tested on.
>>
>> As always, everyone is encouraged to vote, including non-committers.
>>
>> This vote will close in the usual 72 hours from now, i.e., on
>> Tuesday, 10/23 at 5:00 PM US/Mountain time. Follow the link
>> below for the countdown:
>> http://tinyurl.com/2h5f73
>>
>>
>
>
Re: [VOTE] release stdcxx 4.2.0 (candidate 7)
Posted by Liviu Nicoara <li...@roguewave.com>.
+1.
Martin Sebor wrote:
> I just created the next stdcxx 4.2.0 release candidate tag,
> stdcxx-4.2.0-rc-7, that incorporates changes addressing issues
> pointed out in the original vote thread.
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/
>
> The tarball containing the release candidate sources can be
> downloaded from my home directory at the following link:
> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/stdcxx-incubating-4.2.0.tar.gz
>
>
> The MD5 sum for the tarball is: b43adeb0c72cf4747301818f4dff4fa1
>
> Instructions on unpacking the tarball, configuring and building
> the library and the set of examples and tests, are in the README
> file contained in the tarball and can also be viewed directly
> in Subversion:
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/README
>
> The Jira "Release Notes" for 4.2.0 detailing the issues resolved
> in this release can be viewed here:
> http://tinyurl.com/ytzonz
>
> stdcxx 4.2.0 has been tested on the set of platforms listed in
> the README. The test results for most of the tested platforms
> can be be viewed on the following page:
> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/results/
> (there are a few failures, most of them attributable to issues in
> the Rogue Wave test infrastructure; a small number of failures are
> due to known stdcxx issues).
>
> Please download and test the tarball and vote to approve the
> release and to request the approval of the Incubator PMC to publish
> it on the stdcxx site. In your vote, please include the names and
> versions of the compilers and operating systems that you tested on.
>
> As always, everyone is encouraged to vote, including non-committers.
>
> This vote will close in the usual 72 hours from now, i.e., on
> Tuesday, 10/23 at 5:00 PM US/Mountain time. Follow the link
> below for the countdown:
> http://tinyurl.com/2h5f73
>
>
--
Your fault - core dumped.
RE: [VOTE] release stdcxx 4.2.0 (candidate 7)
Posted by Farid Zaripov <Fa...@epam.com>.
> -----Original Message-----
> From: Martin Sebor [mailto:sebor@roguewave.com]
> Sent: Sunday, October 21, 2007 1:55 AM
> To: stdcxx-dev@incubator.apache.org
> Subject: [VOTE] release stdcxx 4.2.0 (candidate 7)
>
> I just created the next stdcxx 4.2.0 release candidate tag,
> stdcxx-4.2.0-rc-7, that incorporates changes addressing
> issues pointed out in the original vote thread.
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/
>
> The tarball containing the release candidate sources can be
> downloaded from my home directory at the following link:
> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/stdcxx-incub
> ating-4.2.0.tar.gz
>
> Please download and test the tarball and vote to approve the
> release and to request the approval of the Incubator PMC to
> publish it on the stdcxx site. In your vote, please include
> the names and versions of the compilers and operating systems
> that you tested on.
I've tested on MSVC 7.1, 32-bit and 64-bit MSVC 8 ICC 9.1 ICC 10.0
and the test are succeeded, so +1 from me.
>
> As always, everyone is encouraged to vote, including non-committers.
>
> This vote will close in the usual 72 hours from now, i.e., on
> Tuesday, 10/23 at 5:00 PM US/Mountain time. Follow the link
> below for the countdown:
> http://tinyurl.com/2h5f73
Farid.
RE: [VOTE RESULT] release stdcxx 4.2.0 (candidate 7)
Posted by Martin Sebor <se...@roguewave.com>.
Farid Zaripov-2 wrote:
>
>> -----Original Message-----
>> From: Martin Sebor [mailto:sebor@roguewave.com]
>> Sent: Wednesday, October 24, 2007 4:28 AM
>> To: stdcxx-dev@incubator.apache.org
>> Subject: [VOTE RESULT] release stdcxx 4.2.0 (candidate 7)
>>
>>
>> The vote passes with 5 +1 binding votes:
>>
>> Andrew Black
>> Farid Zaripov
>> Liviu Nicoara
>> Mark Brown
>> Martin Sebor
>>
>> No other votes were recorded.
>>
>> I'll go ahead and open another vote on egeneral@a.i.o shortly
>> to get the IPMC's approval to publish the release.
>
> I've reopened the STDCXX-552 issue (which is blocker for 4.2.0)
> because I've found 75 files with the old ASL headers in
> stdcxx-incubating-4.2.0.tar.gz.
>
> Now I'm starting making the patch, but maybe it's not so important for
> 4.2.0
> since the RAT tool was passed on these files?
>
> Farid.
>
>
Right. As Thilo just reported on general@a.i.o, RAT is happy. See
http://www.nabble.com/Re%3A--VOTE--approve-stdcxx-4.2.0-release-p13430768.html
The old headers should be changed, but we should do it under a separate
issue from STDCXX-552. The last thing we want is to give the impression
that we still have a serious legal issue in 4.2.0 now that the IPMC is
voting
to approve the release.
Martin
--
View this message in context: http://www.nabble.com/-VOTE--release-stdcxx-4.2.0-tf4650691.html#a13431011
Sent from the stdcxx-dev mailing list archive at Nabble.com.
RE: [VOTE RESULT] release stdcxx 4.2.0 (candidate 7)
Posted by Farid Zaripov <Fa...@epam.com>.
> -----Original Message-----
> From: Martin Sebor [mailto:sebor@roguewave.com]
> Sent: Wednesday, October 24, 2007 4:28 AM
> To: stdcxx-dev@incubator.apache.org
> Subject: [VOTE RESULT] release stdcxx 4.2.0 (candidate 7)
>
>
> The vote passes with 5 +1 binding votes:
>
> Andrew Black
> Farid Zaripov
> Liviu Nicoara
> Mark Brown
> Martin Sebor
>
> No other votes were recorded.
>
> I'll go ahead and open another vote on egeneral@a.i.o shortly
> to get the IPMC's approval to publish the release.
I've reopened the STDCXX-552 issue (which is blocker for 4.2.0)
because I've found 75 files with the old ASL headers in
stdcxx-incubating-4.2.0.tar.gz.
Now I'm starting making the patch, but maybe it's not so important for
4.2.0
since the RAT tool was passed on these files?
Farid.
[VOTE RESULT] release stdcxx 4.2.0 (candidate 7)
Posted by Martin Sebor <se...@roguewave.com>.
The vote passes with 5 +1 binding votes:
Andrew Black
Farid Zaripov
Liviu Nicoara
Mark Brown
Martin Sebor
No other votes were recorded.
I'll go ahead and open another vote on egeneral@a.i.o shortly to get
the IPMC's approval to publish the release.
Thanks
Martin
Martin Sebor wrote:
>
> I just created the next stdcxx 4.2.0 release candidate tag,
> stdcxx-4.2.0-rc-7, that incorporates changes addressing issues
> pointed out in the original vote thread.
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/
>
> The tarball containing the release candidate sources can be
> downloaded from my home directory at the following link:
> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/stdcxx-incubating-4.2.0.tar.gz
>
> The MD5 sum for the tarball is: b43adeb0c72cf4747301818f4dff4fa1
>
> Instructions on unpacking the tarball, configuring and building
> the library and the set of examples and tests, are in the README
> file contained in the tarball and can also be viewed directly
> in Subversion:
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/README
>
> The Jira "Release Notes" for 4.2.0 detailing the issues resolved
> in this release can be viewed here:
> http://tinyurl.com/ytzonz
>
> stdcxx 4.2.0 has been tested on the set of platforms listed in
> the README. The test results for most of the tested platforms
> can be be viewed on the following page:
> http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/results/
> (there are a few failures, most of them attributable to issues in
> the Rogue Wave test infrastructure; a small number of failures are
> due to known stdcxx issues).
>
> Please download and test the tarball and vote to approve the
> release and to request the approval of the Incubator PMC to publish
> it on the stdcxx site. In your vote, please include the names and
> versions of the compilers and operating systems that you tested on.
>
> As always, everyone is encouraged to vote, including non-committers.
>
> This vote will close in the usual 72 hours from now, i.e., on
> Tuesday, 10/23 at 5:00 PM US/Mountain time. Follow the link
> below for the countdown:
> http://tinyurl.com/2h5f73
>
>
>
--
View this message in context: http://www.nabble.com/-VOTE--release-stdcxx-4.2.0-tf4650691.html#a13377405
Sent from the stdcxx-dev mailing list archive at Nabble.com.
[VOTE] release stdcxx 4.2.0 (candidate 7)
Posted by Martin Sebor <se...@roguewave.com>.
I just created the next stdcxx 4.2.0 release candidate tag,
stdcxx-4.2.0-rc-7, that incorporates changes addressing issues
pointed out in the original vote thread.
http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/
The tarball containing the release candidate sources can be
downloaded from my home directory at the following link:
http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/stdcxx-incubating-4.2.0.tar.gz
The MD5 sum for the tarball is: b43adeb0c72cf4747301818f4dff4fa1
Instructions on unpacking the tarball, configuring and building
the library and the set of examples and tests, are in the README
file contained in the tarball and can also be viewed directly
in Subversion:
http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-7/README
The Jira "Release Notes" for 4.2.0 detailing the issues resolved
in this release can be viewed here:
http://tinyurl.com/ytzonz
stdcxx 4.2.0 has been tested on the set of platforms listed in
the README. The test results for most of the tested platforms
can be be viewed on the following page:
http://people.apache.org/~sebor/stdcxx-4.2.0-rc-7/results/
(there are a few failures, most of them attributable to issues in
the Rogue Wave test infrastructure; a small number of failures are
due to known stdcxx issues).
Please download and test the tarball and vote to approve the
release and to request the approval of the Incubator PMC to publish
it on the stdcxx site. In your vote, please include the names and
versions of the compilers and operating systems that you tested on.
As always, everyone is encouraged to vote, including non-committers.
This vote will close in the usual 72 hours from now, i.e., on
Tuesday, 10/23 at 5:00 PM US/Mountain time. Follow the link
below for the countdown:
http://tinyurl.com/2h5f73
Re: [VOTE] release stdcxx 4.2.0
Posted by Martin Sebor <se...@roguewave.com>.
Mark Brown wrote:
> Martin Sebor wrote:
>> I created what I'm hoping will be the final stdcxx 4.2.0 release
>> candidate, stdcxx-4.2.0-rc-6:
>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-6/
>>
>> along with a tarball containing the sources:
>> http://people.apache.org/~sebor/stdcxx/stdcxx-incubating-4.2.0.tar.gz
>>
>> The MD5 sum for the tarball is: f65ea507f7d82688d1cf241bce25dc01
>>
>> Instructions on unpacking the tarball, configuring the library,
>> and building it along with the set of examples and tests, are
>> in the README file contained in the tarball. The file can also
>> be viewed directly in Subversion:
>> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-6/README
>>
>> The Jira "Release Notes" for 4.2.0 detailing the vast number of
>> issues resolved in this release can be found here:
>> http://tinyurl.com/ytzonz
>>
>> stdcxx 4.2.0 has been tested on the set of platforms listed in
>> the README. The test results for most of the tested platforms
>> can be be viewed on the following page:
>> http://people.apache.org/~sebor/stdcxx/results/
>> (there are some failures, most of them due to the Rogue Wave test
>> infrastructure and IT issues; please disregard those).
>>
>> Please take the tarball for a spin and vote to approve the release
>> and to request the approval of the Incubator PMC to publish it on
>> our site.
>>
>> Everyone is encouraged to vote, including non-committers.
>>
>> This vote will close in the usual 72 hours.
>
> +0, mainly because not all tests compiled.
>
> I confirmed that the binary compatibility issue with limits has
> been resolved in 12D and 11D buildtypes. Great job you guys!
Thanks. It wasn't easy.
>
> Compiling the library with gcc 4.1.2 with optimization on is clean
> with the exception of the two warnings below. This is a regression
> from 4.1.3 which is free of these warnings.
This is actually a known issue although we didn't realize that
it was a regression -- see:
http://issues.apache.org/jira/browse/STDCXX-350
> I also saw a number
> of the same warnings in the examples and the test driver. I don't
> know much about strict aliasing to judge if the warnings indicate
> actual problems or if they are safe to ignore. Either way, I don't
> necessarily see them as a reason to hold up the release. There
> also are many warnings about not being able inline some functions.
I don't know much about the consequences of breaking the gcc
strict aliasing rules either, but from the little I've read
online it sounds like they could be pretty dire because the
compiler apparently doesn't do a full data flow analysis and
might lose track of the fact that the same piece of data is
being accessed through two different pointers (or something
like that). Since it's a regression , the fix is easy and
non-invasive, and since we've already made a change to 4.2.0
that will require us to create another candidate we might as
well err on the side of caution and fix it. I've tested and
committed the following change:
http://svn.apache.org/viewvc?rev=586811&view=rev
>
> Besides the warnings, the test 26.valarray.cassign.cpp gave many
> compiler errors (see the attached log file) All other tests and
> examples compiled okay, although many with warnings. I don't know
> the stdcxx policy regarding compiler errors in tests but if the
> test compilation errors are a known issue (STDCXX-512?) we might
> want to disable the test in 4.2.0.
Agreed. I disabled the problematic specialization with this
change:
http://svn.apache.org/viewvc?rev=586808&view=rev.
Martin
>
> --Mark
>
> /home/mbrown/stdcxx-4.2.0/src/ctype.cpp: In constructor
> ‘std::ctype_byname<char>::ctype_byname(const char*, long unsigned int)’:
> /home/mbrown/stdcxx-4.2.0/src/ctype.cpp:944: warning: dereferencing
> type-punned pointer will break strict-aliasing rules
>
> /home/mbrown/stdcxx-4.2.0/include/rw/_rawiter.h: In function ‘void
> std::return_temporary_buffer(_TypeT*) [with _TypeT =
> std::ios_base::_C_usr_data::_C_event_cb]’:
> /home/mbrown/stdcxx-4.2.0/src/iostore.cpp:151: instantiated from here
> /home/mbrown/stdcxx-4.2.0/include/rw/_rawiter.h:164: warning:
> dereferencing type-punned pointer will break strict-aliasing rules
> /home/mbrown/stdcxx-4.2.0/include/rw/_rawiter.h: In function
> ‘std::pair<_TypeT*, _Distance> std::get_temporary_buffer(_Distance,
> _TypeT*) [with _TypeT = std::ios_base::_C_usr_data::_C_event_cb,
> _Distance = long int]’:
> /home/mbrown/stdcxx-4.2.0/include/rw/_rawiter.h:153: instantiated from
> ‘std::pair<_TypeT*, long int> std::get_temporary_buffer(long int) [with
> _TypeT = std::ios_base::_C_usr_data::_C_event_cb]’
> /home/mbrown/stdcxx-4.2.0/src/iostore.cpp:120: instantiated from here
> /home/mbrown/stdcxx-4.2.0/include/rw/_rawiter.h:138: warning:
> dereferencing type-punned pointer will break strict-aliasing rules
> g
Re: [VOTE] release stdcxx 4.2.0
Posted by Mark Brown <ma...@gmail.com>.
Martin Sebor wrote:
> I created what I'm hoping will be the final stdcxx 4.2.0 release
> candidate, stdcxx-4.2.0-rc-6:
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-6/
>
> along with a tarball containing the sources:
> http://people.apache.org/~sebor/stdcxx/stdcxx-incubating-4.2.0.tar.gz
>
> The MD5 sum for the tarball is: f65ea507f7d82688d1cf241bce25dc01
>
> Instructions on unpacking the tarball, configuring the library,
> and building it along with the set of examples and tests, are
> in the README file contained in the tarball. The file can also
> be viewed directly in Subversion:
> http://svn.apache.org/repos/asf/incubator/stdcxx/tags/4.2.0-rc-6/README
>
> The Jira "Release Notes" for 4.2.0 detailing the vast number of
> issues resolved in this release can be found here:
> http://tinyurl.com/ytzonz
>
> stdcxx 4.2.0 has been tested on the set of platforms listed in
> the README. The test results for most of the tested platforms
> can be be viewed on the following page:
> http://people.apache.org/~sebor/stdcxx/results/
> (there are some failures, most of them due to the Rogue Wave test
> infrastructure and IT issues; please disregard those).
>
> Please take the tarball for a spin and vote to approve the release
> and to request the approval of the Incubator PMC to publish it on
> our site.
>
> Everyone is encouraged to vote, including non-committers.
>
> This vote will close in the usual 72 hours.
+0, mainly because not all tests compiled.
I confirmed that the binary compatibility issue with limits has
been resolved in 12D and 11D buildtypes. Great job you guys!
Compiling the library with gcc 4.1.2 with optimization on is clean
with the exception of the two warnings below. This is a regression
from 4.1.3 which is free of these warnings. I also saw a number
of the same warnings in the examples and the test driver. I don't
know much about strict aliasing to judge if the warnings indicate
actual problems or if they are safe to ignore. Either way, I don't
necessarily see them as a reason to hold up the release. There
also are many warnings about not being able inline some functions.
Besides the warnings, the test 26.valarray.cassign.cpp gave many
compiler errors (see the attached log file) All other tests and
examples compiled okay, although many with warnings. I don't know
the stdcxx policy regarding compiler errors in tests but if the
test compilation errors are a known issue (STDCXX-512?) we might
want to disable the test in 4.2.0.
--Mark
/home/mbrown/stdcxx-4.2.0/src/ctype.cpp: In constructor
‘std::ctype_byname<char>::ctype_byname(const char*, long unsigned int)’:
/home/mbrown/stdcxx-4.2.0/src/ctype.cpp:944: warning: dereferencing
type-punned pointer will break strict-aliasing rules
/home/mbrown/stdcxx-4.2.0/include/rw/_rawiter.h: In function ‘void
std::return_temporary_buffer(_TypeT*) [with _TypeT =
std::ios_base::_C_usr_data::_C_event_cb]’:
/home/mbrown/stdcxx-4.2.0/src/iostore.cpp:151: instantiated from here
/home/mbrown/stdcxx-4.2.0/include/rw/_rawiter.h:164: warning:
dereferencing type-punned pointer will break strict-aliasing rules
/home/mbrown/stdcxx-4.2.0/include/rw/_rawiter.h: In function
‘std::pair<_TypeT*, _Distance> std::get_temporary_buffer(_Distance,
_TypeT*) [with _TypeT = std::ios_base::_C_usr_data::_C_event_cb,
_Distance = long int]’:
/home/mbrown/stdcxx-4.2.0/include/rw/_rawiter.h:153: instantiated from
‘std::pair<_TypeT*, long int> std::get_temporary_buffer(long int) [with
_TypeT = std::ios_base::_C_usr_data::_C_event_cb]’
/home/mbrown/stdcxx-4.2.0/src/iostore.cpp:120: instantiated from here
/home/mbrown/stdcxx-4.2.0/include/rw/_rawiter.h:138: warning:
dereferencing type-punned pointer will break strict-aliasing rules
g