[jira] Commented: (STDCXX-430) building Boost with stdcxx
[ https://issues.apache.org/jira/browse/STDCXX-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12555608#action_12555608 ] Martin Sebor commented on STDCXX-430: - As noted in the post below, Boost regression test results with stdcxx have been published here: http://beta.boost.org/development/tests/trunk/developer/summary.html http://www.nabble.com/Running-the-boost-regression-tests-with-stdcxx-td14536939.html#a14536939 building Boost with stdcxx -- Key: STDCXX-430 URL: https://issues.apache.org/jira/browse/STDCXX-430 Project: C++ Standard Library Issue Type: Improvement Components: External Affects Versions: 4.2.0 Reporter: Martin Sebor Assignee: Farid Zaripov Priority: Critical Fix For: 4.2.1 Attachments: boost-1.34.1.patch, boost_regress_gcc.zip, boost_regress_sun.zip, boost_regress_win.zip This is a placeholder issue to make it possible and easy to build the Boost libraries on top of stdcxx. Each stdcxx bug revealed by Boost must have an issue. The issue should be linked to this one. Changes contributed to Boost (such as stdcxx .jam files) should be tracked as subtasks of this issue. Each bug in Boost should be filed in the Boost bug tracking database and cross-referenced in comments on this issue. See the following threads for details of the project: http://www.mail-archive.com/stdcxx-dev@incubator.apache.org/msg02910.html http://www.mail-archive.com/stdcxx-dev@incubator.apache.org/msg03089.html http://www.mail-archive.com/stdcxx-dev@incubator.apache.org/msg03410.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (STDCXX-536) allow thread safety tests to time out without failing
[ https://issues.apache.org/jira/browse/STDCXX-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Sebor updated STDCXX-536: Severity: Usability Patch Info: [Patch Available] Set Severity to Usability and checked Patch Available. allow thread safety tests to time out without failing - Key: STDCXX-536 URL: https://issues.apache.org/jira/browse/STDCXX-536 Project: C++ Standard Library Issue Type: Improvement Components: Tests Affects Versions: 4.2.0 Reporter: Martin Sebor Assignee: Travis Vitek Fix For: 4.2.1 Attachments: stdcxx-536.patch The newly added thread safety tests (and possibly some of the existing ones) tend to run for a long time, consuming a lot of CPU cycles, and sometimes even failing due to a timeout (currently 300 seconds in nightly builds). It would be useful to provide a mechanism such as a command line option whereby the tests' runtime could be limited without necessarily causing them to fail when the amount of time is exceeded. One way to do it would be for each test to set an alarm in response to this command line option and in handler for the alarm set a flag that each thread would check at each iteration of its loop to see if it should break. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (STDCXX-536) allow thread safety tests to time out without failing
[ https://issues.apache.org/jira/browse/STDCXX-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12555652#action_12555652 ] Martin Sebor commented on STDCXX-536: - I'm not sure where we left this issue. The discussion kind of petered out... Do we want the patch or not? allow thread safety tests to time out without failing - Key: STDCXX-536 URL: https://issues.apache.org/jira/browse/STDCXX-536 Project: C++ Standard Library Issue Type: Improvement Components: Tests Affects Versions: 4.2.0 Reporter: Martin Sebor Assignee: Travis Vitek Fix For: 4.2.1 Attachments: stdcxx-536.patch The newly added thread safety tests (and possibly some of the existing ones) tend to run for a long time, consuming a lot of CPU cycles, and sometimes even failing due to a timeout (currently 300 seconds in nightly builds). It would be useful to provide a mechanism such as a command line option whereby the tests' runtime could be limited without necessarily causing them to fail when the amount of time is exceeded. One way to do it would be for each test to set an alarm in response to this command line option and in handler for the alarm set a flag that each thread would check at each iteration of its loop to see if it should break. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (STDCXX-536) allow thread safety tests to time out without failing
[ https://issues.apache.org/jira/browse/STDCXX-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12555660#action_12555660 ] Travis Vitek commented on STDCXX-536: - The patch is not ready for submission. I think we need to pick up discussion on this issue again. allow thread safety tests to time out without failing - Key: STDCXX-536 URL: https://issues.apache.org/jira/browse/STDCXX-536 Project: C++ Standard Library Issue Type: Improvement Components: Tests Affects Versions: 4.2.0 Reporter: Martin Sebor Assignee: Travis Vitek Fix For: 4.2.1 Attachments: stdcxx-536.patch The newly added thread safety tests (and possibly some of the existing ones) tend to run for a long time, consuming a lot of CPU cycles, and sometimes even failing due to a timeout (currently 300 seconds in nightly builds). It would be useful to provide a mechanism such as a command line option whereby the tests' runtime could be limited without necessarily causing them to fail when the amount of time is exceeded. One way to do it would be for each test to set an alarm in response to this command line option and in handler for the alarm set a flag that each thread would check at each iteration of its loop to see if it should break. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (STDCXX-240) #define _RWSTD_NO_EXCEPTIONS when exceptions are disabled via command line option
[ https://issues.apache.org/jira/browse/STDCXX-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Travis Vitek updated STDCXX-240: Patch Info: [Patch Available] #define _RWSTD_NO_EXCEPTIONS when exceptions are disabled via command line option - Key: STDCXX-240 URL: https://issues.apache.org/jira/browse/STDCXX-240 Project: C++ Standard Library Issue Type: Improvement Components: Build Affects Versions: 4.1.2, 4.1.3, 4.1.4 Reporter: Martin Sebor Assignee: Travis Vitek Priority: Minor Fix For: 4.2.1 Attachments: stdcxx-240-vacpp60.patch, stdcxx-240.patch Moved from the Rogue Wave bug tracking database: Class/File: stdcomp.h Fix Priority: Can Fix Long Description: *** Dec 1 1999 6:03PM *** sebor *** A request for enhancement. Subject: define RWSTD_NO_EXCEPTIONS when __HPACC_NOEH is Date: Wed, 01 Dec 1999 17:11:36 -0800 From: Chichiang Wan [EMAIL PROTECTED] Organization: California Language Labs To: oemsupport [EMAIL PROTECTED] CC: [EMAIL PROTECTED], wanc_at_hp [EMAIL PROTECTED] aCC has an option +noeh. When it is provided, __HPACC_NOEH will be defined. It would be nice for users to need to only use +noeh. For that, RWSTD_NO_EXCEPTIONS needs to be defined conditionally. = $ cat test.C #include string $ aCC +noeh -c test.C Error 46: /opt/aCC/include/memory, line 493 # Exception handling is not enabled (do not use the +noeh flag to aCC). RWSTD_THROW_NO_MSG(tmp == 0, bad_alloc); -- Chichiang Modified By: sebor @ May 29, 2000 10:28:25 PM We should do this AND test it -- not just on aCC but in general with all compilers that support this feature. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (STDCXX-240) #define _RWSTD_NO_EXCEPTIONS when exceptions are disabled via command line option
[ https://issues.apache.org/jira/browse/STDCXX-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Travis Vitek closed STDCXX-240. --- Resolution: Fixed Closing. #define _RWSTD_NO_EXCEPTIONS when exceptions are disabled via command line option - Key: STDCXX-240 URL: https://issues.apache.org/jira/browse/STDCXX-240 Project: C++ Standard Library Issue Type: Improvement Components: Build Affects Versions: 4.1.2, 4.1.3, 4.1.4 Reporter: Martin Sebor Assignee: Travis Vitek Priority: Minor Fix For: 4.2.1 Attachments: stdcxx-240-vacpp60.patch, stdcxx-240.patch Moved from the Rogue Wave bug tracking database: Class/File: stdcomp.h Fix Priority: Can Fix Long Description: *** Dec 1 1999 6:03PM *** sebor *** A request for enhancement. Subject: define RWSTD_NO_EXCEPTIONS when __HPACC_NOEH is Date: Wed, 01 Dec 1999 17:11:36 -0800 From: Chichiang Wan [EMAIL PROTECTED] Organization: California Language Labs To: oemsupport [EMAIL PROTECTED] CC: [EMAIL PROTECTED], wanc_at_hp [EMAIL PROTECTED] aCC has an option +noeh. When it is provided, __HPACC_NOEH will be defined. It would be nice for users to need to only use +noeh. For that, RWSTD_NO_EXCEPTIONS needs to be defined conditionally. = $ cat test.C #include string $ aCC +noeh -c test.C Error 46: /opt/aCC/include/memory, line 493 # Exception handling is not enabled (do not use the +noeh flag to aCC). RWSTD_THROW_NO_MSG(tmp == 0, bad_alloc); -- Chichiang Modified By: sebor @ May 29, 2000 10:28:25 PM We should do this AND test it -- not just on aCC but in general with all compilers that support this feature. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (STDCXX-195) [Linux] error on std::putc()
[
https://issues.apache.org/jira/browse/STDCXX-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12555762#action_12555762
]
Martin Sebor commented on STDCXX-195:
-
Same problem with getc():
$ cat t.cpp make t
#include cstdio
int main()
{
std::putc ('x', stdout);
std::getc (stdin);
}
gcc -c -I/home/sebor/stdcxx/include/ansi -D_RWSTDDEBUG -pthread
-I/home/sebor/stdcxx/include -I/build/sebor/stdcxx-gcc-4.1.2-15D/include
-I/home/sebor/stdcxx/examples/include -pedantic -nostdinc++ -g -W -Wall
-Wcast-qual -Winline -Wshadow -Wwrite-strings -Wno-long-long -Wcast-align
t.cpp
t.cpp: In function 'int main()':
t.cpp:5: error: '_IO_putc' is not a member of 'std'
t.cpp:6: error: '_IO_getc' is not a member of 'std'
make: *** [t.o] Error 1
[Linux] error on std::putc()
Key: STDCXX-195
URL: https://issues.apache.org/jira/browse/STDCXX-195
Project: C++ Standard Library
Issue Type: Bug
Components: 27. Input/Output
Affects Versions: 4.1.3
Environment: SuSE SLES 9sp2 (ppc64), IBM XL C/C++ Advanced Edition
V8.0 for Linux
Version: 08.00..
Reporter: Scott (Yu) Zhong
Assignee: Martin Sebor
Fix For: 4.2.1
IBM VAC++ 8.0 linux uses _IO_putc instead of putc
file affected:
include/ansi/cstdio
--- testcase.cpp
#include cstdio
int main()
{
std::putc (test, stdout);
std::fflush (stdout);
}
-- compile line
xlc -F /package/1/ppc64/compilers/ibm/va80/vac.cfg -q64 -qarch=ppc64
-D_RWSTD_NO_IMPLICIT_INCLUSION -qnolib -Wl,-dynamic-linker
-Wl,/lib64/ld64.so.1 -D_RWCONFIG=stdlib_rs -I../../include
-I./../../../../include -I./../../../../include/ansi -I./../../../.. -I.. -I.
-g -c ../testcase.cpp
-- output --
../testcase.cpp, line 5.9: 1540-0130 (S) std::_IO_putc is not declared.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
