Speaking of other changes that might need to be integrated
before we tag the branch, here are a couple more:
https://issues.apache.org/jira/browse/STDCXX-479
https://issues.apache.org/jira/browse/STDCXX-481
Martin
Martin Sebor wrote:
Andrew, we should be using the -rcN tag rather than the
Looking at JIRA, it appears the files that will need to be branched for
these changes are
/incubator/stdcxx/trunk/GNUmakefile
/incubator/stdcxx/trunk/etc/config/GNUmakefile.cfg
/incubator/stdcxx/trunk/etc/config/makefile.rules
/incubator/stdcxx/trunk/etc/config/sunpro.config
In addition, we'll
Andrew Black wrote:
Looking at JIRA, it appears the files that will need to be branched for
these changes are
/incubator/stdcxx/trunk/GNUmakefile
/incubator/stdcxx/trunk/etc/config/GNUmakefile.cfg
/incubator/stdcxx/trunk/etc/config/makefile.rules
/incubator/stdcxx/trunk/etc/config/sunpro.config
[
https://issues.apache.org/jira/browse/STDCXX-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-517:
Affects Version/s: (was: 4.2)
4.1.3
This affects 4.1.3. I'll let Farid
Andrew Black wrote:
Greetings all.
I've taken a little time to glance over the open tasks which I reported
but have not been assigned. My analysis of these issues is as follows:
336 (allow multiple config.h files in the same installation directory)
Marked as critical for the 4.2.0
[
https://issues.apache.org/jira/browse/STDCXX-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-525.
---
Resolution: Fixed
A successful pthreads build from last night confirms the patch took care of it.
[
https://issues.apache.org/jira/browse/STDCXX-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-516:
Affects Version/s: (was: 4.2)
4.1.3
Same as STDCXX-517: affects 4.1.3.
[
https://issues.apache.org/jira/browse/STDCXX-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-483:
Affects Version/s: 4.1.3
Fix Version/s: 4.2.1
Scheduled for 4.2.1 at the earliest.
add
[
https://issues.apache.org/jira/browse/STDCXX-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor updated STDCXX-475:
Affects Version/s: trunk
Fix Version/s: 4.2
This affects the trunk (and the pre-release
[
https://issues.apache.org/jira/browse/STDCXX-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-475.
---
Resolution: Fixed
Fixed by the just committed change.
[Intel C++ 10.0.025/Linux] ICE in
[
https://issues.apache.org/jira/browse/STDCXX-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Black closed STDCXX-361.
---
Resolution: Won't Fix
Nightly testing has confirmed that this issue was resolved in later versions
[
https://issues.apache.org/jira/browse/STDCXX-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Black closed STDCXX-362.
---
Resolution: Won't Fix
Fix Version/s: (was: 4.2)
Resolving as Won't Fix, as this can be
[
https://issues.apache.org/jira/browse/STDCXX-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Vitek updated STDCXX-528:
Attachment: 22.locale.money.get.mt.cpp
test implementation
create test
Everton Araujo wrote:
Thank you Martin and Andrew for helping me.
Below is the patch for STDCXX-522 (std::filebuf::overflow(EOF) writes EOF to
file in unbuffered mode)
I have one other question for you about this patch, Everton:
Index: include/fstream.cc
[
https://issues.apache.org/jira/browse/STDCXX-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Vitek updated STDCXX-529:
Attachment: (was: 22.locale.time.get.mt.cpp)
create test 22.locale.time.get.mt.cpp
[
https://issues.apache.org/jira/browse/STDCXX-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Vitek updated STDCXX-529:
Attachment: 22.locale.time.get.mt.cpp
cleanup and simplify test. ready for review.
create test
[
https://issues.apache.org/jira/browse/STDCXX-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Travis Vitek updated STDCXX-530:
Attachment: 22.locale.num.get.mt.cpp
create test 22.locale.num.get.mt.cpp
Travis, this test looks too good -- there's nothing for me to pick
on, not even formatting! ;-)
I'm running it on a 4 CPU dual core Xeon against a locally modified
trunk and so far so good. Has it ever failed in your tests?
Martin
Travis Vitek (JIRA) wrote:
[
[
https://issues.apache.org/jira/browse/STDCXX-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Black updated STDCXX-366:
Fix Version/s: 4.2.1
Scheduling for 4.2.1, though it may be differed again.
Add benchmarking
[
https://issues.apache.org/jira/browse/STDCXX-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Black updated STDCXX-261:
Fix Version/s: 4.2.1
Scheduling for 4.2.1, though it may be deferred again.
runall should parse
Martin Sebor wrote:
Travis, this test looks too good -- there's nothing for me to pick
on, not even formatting! ;-)
I'm _finally_ getting used to it.
I'm running it on a 4 CPU dual core Xeon against a locally modified
trunk and so far so good. Has it ever failed in your tests?
I have yet
So a quick question. I've got all of those sub-tasks created, and I've
finished writing up the tests for a few of them. I'm wondering when it
is appropriate to resolve the sub-tasks. Should I wait until the tests
have been accepted, submitted, or until they have run on all platforms
in nightly
Travis Vitek wrote:
So a quick question. I've got all of those sub-tasks created, and I've
finished writing up the tests for a few of them. I'm wondering when it
is appropriate to resolve the sub-tasks. Should I wait until the tests
have been accepted, submitted, or until they have run on all
I'm looking at the thread safety test results across platforms
and I'm puzzled by the Windows data. On other platforms, the
22.locale.num.put.mt test takes up to three minutes (at which
point it times out because we don't let tests run longer than
that) to either complete or crash. But in some of
Travis Vitek wrote:
[...]
I have yet to see a failure in the num_get.mt test.
Isn't that odd, though? The num_put test does fail, even if not
consistently, and the numpunct one fails pretty much at the drop
of a hat. I don't think they fail because of a bug in the facets
themselves but
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
[EMAIL PROTECTED] wrote:
Author: ablack
Date: Fri Aug 24 17:29:23 2007
New Revision: 569584
URL: http://svn.apache.org/viewvc?rev=569584view=rev
Log:
2007-08-24 Andrew Black [EMAIL PROTECTED]
STDCXX-470
STDCXX-479
STDCXX-481
FWIW, this change doesn't fix these bugs,
I wonder if this is related to the rw_locales() issue on windows
systems? Those locale tests significantly longer with 32 locales than
they do with just C locale.
Travis
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Friday, August 24, 2007 6:21 PM
To:
28 matches
Mail list logo
