[VOTE] release stdcxx 4.2.0
|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 | Next > |
 |
[VOTE] release stdcxx 4.2.0
by Martin Sebor
::
Rate this Message:
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
by Andrew Black-5
::
Rate this Message:
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@...%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
by Martin Sebor
::
Rate this Message:
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@...%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
by Travis Vitek-4
::
Rate this Message:
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
by Travis Vitek-4
::
Rate this Message:
2007-10-19 Travis Vitek <vitek@...> * 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@...] >Sent: Friday, October 19, 2007 11:19 AM >To: stdcxx-dev@... >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
by Martin Sebor
::
Rate this Message:
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 <vitek@...> > > * 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@...] >> Sent: Friday, October 19, 2007 11:19 AM >> To: stdcxx-dev@... >> 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
by Mark Brown
::
Rate this Message:
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 |
|
|
Re: [VOTE] release stdcxx 4.2.0
by Martin Sebor
::
Rate this Message:
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 |
|
|
[VOTE] release stdcxx 4.2.0 (candidate 7)
by Martin Sebor
::
Rate this Message:
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)
by Liviu Nicoara-2
::
Rate this Message:
+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)
by Martin Sebor
::
Rate this Message:
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)
by Liviu Nicoara-2
::
Rate this Message:
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)
by Martin Sebor
::
Rate this Message:
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: |
