Re: merge fix for STDCXX-501 to 4.2

This is now done: http://svn.apache.org/viewvc?rev=574783&view=rev Martin Sebor wrote: > > I plan to merge the fix below to 4.2. The change implements > a long-awaited solution to a binary incompatibility problem > between stdcxx and code compiled with HP aCC with the -AA > option as described

[jira] Resolved: (STDCXX-549) [Sun C++ 5.9/Linux/x86_64] configuration error on -xarch=generic64

[ https://issues.apache.org/jira/browse/STDCXX-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Sebor resolved STDCXX-549. - Resolution: Fixed Fix Version/s: trunk Fixed by the referenced patch. > [Sun C++ 5.9/Linu

[jira] Closed: (STDCXX-549) [Sun C++ 5.9/Linux/x86_64] configuration error on -xarch=generic64

[ https://issues.apache.org/jira/browse/STDCXX-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Sebor closed STDCXX-549. --- > [Sun C++ 5.9/Linux/x86_64] configuration error on -xarch=generic64 > --

[jira] Assigned: (STDCXX-549) [Sun C++ 5.9/Linux/x86_64] configuration error on -xarch=generic64

[ https://issues.apache.org/jira/browse/STDCXX-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Sebor reassigned STDCXX-549: --- Assignee: Martin Sebor > [Sun C++ 5.9/Linux/x86_64] configuration error on -xarch=generic64 >

[jira] Created: (STDCXX-549) [Sun C++ 5.9/Linux/x86_64] configuration error on -xarch=generic64

[Sun C++ 5.9/Linux/x86_64] configuration error on -xarch=generic64 -- Key: STDCXX-549 URL: https://issues.apache.org/jira/browse/STDCXX-549 Project: C++ Standard Library Issue T

Re: stdcxx atomics

Martin Sebor wrote: Liviu Nicoara wrote: I noticed that -- like other RW libs -- stdcxx does build the atomic ops sources even in ST builds although the logic in rw/_mutex.h picks up the vanilla implementation in 8-11 builds. Is this a mere slip? Yeah, I guess it does. I've never thought abou

[jira] Created: (STDCXX-548) add an internal header for __rw::__rw_get_stdio_fmat()

add an internal header for __rw::__rw_get_stdio_fmat() -- Key: STDCXX-548 URL: https://issues.apache.org/jira/browse/STDCXX-548 Project: C++ Standard Library Issue Type: Improvement

Re: svn commit: r574618 - in /incubator/stdcxx/trunk: README configure.bat generate.bat

Eric Lemings wrote: -Original Message- From: Martin Sebor [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 11, 2007 4:21 PM To: stdcxx-dev@incubator.apache.org Subject: Re: svn commit: r574618 - in /incubator/stdcxx/trunk: README configure.bat generate.bat Since this change affec

Re: stdcxx atomics

Liviu Nicoara wrote: I noticed that -- like other RW libs -- stdcxx does build the atomic ops sources even in ST builds although the logic in rw/_mutex.h picks up the vanilla implementation in 8-11 builds. Is this a mere slip? Yeah, I guess it does. I've never thought about it. It would probab

Re: [jira] Updated: (STDCXX-536) allow thread safety tests to time out without failing

Travis Vitek wrote: [...] I guess I hadn't thought of the fact that some of these tests create multiple thread pools. Hmm. I don't think the test should be allowed to reset its own timeout but I'm not sure I see a good solution. Yeah, ugh. It certainly shouldn't exit successfully without doin

Re: renaming branches/4.2.0 to branches/4.2

William A. Rowe, Jr. wrote: Martin Sebor wrote: Hmm. I admit I hadn't thought of the local checkout problem. Your suggestion sounds most sensible. The only concern I have is that we may not graduate before the release. (I guess I'd better hurry up with the proposal!) Maybe we could do both: leav

RE: [jira] Updated: (STDCXX-536) allow thread safety tests to time out without failing

>Martin Sebor wrote > >Travis Vitek wrote: >> >> >> Whatever timeout period you specify to --timeout-period= >> will be the number of seconds that will elapse before the >> _rw_timeout_expired flag will be set to a non-zero value. >> [...] > >Right. But tests whose threads that don't check the

[jira] Resolved: (STDCXX-493) std::string::append() slow

[ https://issues.apache.org/jira/browse/STDCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Sebor resolved STDCXX-493. - Resolution: Fixed Resolved by the committed patch. The before and after timings posted below ind

[jira] Closed: (STDCXX-493) std::string::append() slow

[ https://issues.apache.org/jira/browse/STDCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Sebor closed STDCXX-493. --- > std::string::append() slow > -- > > Key: STDCXX-493 >

Re: renaming branches/4.2.0 to branches/4.2

Martin Sebor wrote: > > Hmm. I admit I hadn't thought of the local checkout problem. Your > suggestion sounds most sensible. The only concern I have is that > we may not graduate before the release. (I guess I'd better hurry > up with the proposal!) Maybe we could do both: leave 4.2.0 in > place f

Re: renaming branches/4.2.0 to branches/4.2

William A. Rowe, Jr. wrote: Martin Sebor wrote: Just a heads up: I plan to make this change today. If anyone has any concerns, please speak up now. The trouble of course is that you break local checkouts unless those folks use 'svn switch' to flip the repository location. One alternative is t

RE: svn commit: r574618 - in /incubator/stdcxx/trunk: README configure.bat generate.bat

> -Original Message- > From: Martin Sebor [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 11, 2007 4:21 PM > To: stdcxx-dev@incubator.apache.org > Subject: Re: svn commit: r574618 - in > /incubator/stdcxx/trunk: README configure.bat generate.bat > > Since this change affects a use

Re: [jira] Updated: (STDCXX-536) allow thread safety tests to time out without failing

Travis Vitek wrote: Ah, maybe there was some miscommunication in our phone conversation on Friday. When we were talking about this, I mentioned adding a little bit of code to main for the command line argument stuff, and a little code to the thread_func to check the flag in each multithreaded tes

Re: svn commit: r574618 - in /incubator/stdcxx/trunk: README configure.bat generate.bat

Andrew, since we discussed merging Farid's change out to 4.2, I think it would be best to wait until the transient symlink is in place. Martin Martin Sebor wrote: Since this change affects a user interface to the library I think we should provide a migration path for the transition to the new i

Re: renaming branches/4.2.0 to branches/4.2

Martin Sebor wrote: > Just a heads up: I plan to make this change today. If anyone has > any concerns, please speak up now. The trouble of course is that you break local checkouts unless those folks use 'svn switch' to flip the repository location. One alternative is to leave 4.2.0 in place for n

merge fix for STDCXX-501 to 4.2

I plan to merge the fix below to 4.2. The change implements a long-awaited solution to a binary incompatibility problem between stdcxx and code compiled with HP aCC with the -AA option as described in STDCXX-501: http://issues.apache.org/jira/browse/STDCXX-501 http://svn.apache.org/viewvc

Re: renaming branches/4.2.0 to branches/4.2

Just a heads up: I plan to make this change today. If anyone has any concerns, please speak up now. Martin Martin Sebor wrote: While reading the Release Branches section of the Subversion book (http://tinyurl.com/8knxw) I realized that our 4.2.0 release branch would have ideally been named 4.2

Re: svn commit: r574618 - in /incubator/stdcxx/trunk: README configure.bat generate.bat

Since this change affects a user interface to the library I think we should provide a migration path for the transition to the new interface. I suggest we keep generate.bat but make it a symbolic link to configure.bat and deprecate it so that it can be removed in 4.3. Martin [EMAIL PROTECTED] wr

[jira] Commented: (STDCXX-493) std::string::append() slow

[ https://issues.apache.org/jira/browse/STDCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526618 ] Martin Sebor commented on STDCXX-493: - I meant "you DON'T need to add yourself." > std::string::append() slow >

[jira] Commented: (STDCXX-493) std::string::append() slow

[ https://issues.apache.org/jira/browse/STDCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526617 ] Martin Sebor commented on STDCXX-493: - I see. In that case you need to add yourself. To attribute a change to tw

[jira] Commented: (STDCXX-493) std::string::append() slow

[ https://issues.apache.org/jira/browse/STDCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526590 ] Travis Vitek commented on STDCXX-493: - All I did was merge the patch with the current version of the affected fil

[jira] Commented: (STDCXX-493) std::string::append() slow

[ https://issues.apache.org/jira/browse/STDCXX-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526581 ] Martin Sebor commented on STDCXX-493: - If you modified the patch in a substantive way you should add yourself to

[jira] Commented: (STDCXX-117) [Mac OS X 10.2.8] Missing header guards in utility source files

[ https://issues.apache.org/jira/browse/STDCXX-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526578 ] Martin Sebor commented on STDCXX-117: - Andrew, what's the status of this? > [Mac OS X 10.2.8] Missing header gua

[jira] Resolved: (STDCXX-129) [HP aCC] ::wmemcpy et al not declared in

[ https://issues.apache.org/jira/browse/STDCXX-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Sebor resolved STDCXX-129. - Resolution: Fixed Resolved by switching to -AA (see STDCXX-501). The problem still exists when u

allow HTML attachments on stdcxx lists

Hi, Can you please remove text/html from the set of disallowed attachment MIME types on stdcxx mailing lists (stdcxx-dev@incubator.apache.org and [EMAIL PROTECTED])? Some background for this request is here: https://issues.apache.org/jira/browse/INFRA-1194 Thanks Martin

new Jira field: Patch Available

To make bug triage a little easier, I added a new field to stdcxx issues called Patch Available. The field is a check box that should be checked when a patch is attached to an issue. It would help if non-committers who have submitted patches to Jira issues that are ready for review please checked

[jira] Updated: (STDCXX-504) Add Apache copyright notices

[ https://issues.apache.org/jira/browse/STDCXX-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Sebor updated STDCXX-504: Patch Info: [Patch Available] > Add Apache copyright notices > > >

[jira] Closed: (STDCXX-501) [HP aCC 3] compile using -AA rather than -Aa

[ https://issues.apache.org/jira/browse/STDCXX-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Sebor closed STDCXX-501. --- Resolution: Fixed Nightly build results confirm this is working correctly. > [HP aCC 3] compile usin

RE: [jira] Updated: (STDCXX-536) allow thread safety tests to time out without failing

Ah, maybe there was some miscommunication in our phone conversation on Friday. When we were talking about this, I mentioned adding a little bit of code to main for the command line argument stuff, and a little code to the thread_func to check the flag in each multithreaded test. You responded that

Re: Windows build failures

We continue to be having serious problems in our latest results due to what looks like infrastructure or setup issues (we had no updates over the weekend due to a ssh permission issue I ran into last Friday). I isolated the problematic results into the attached page to make it easier to focus on t

[jira] Updated: (STDCXX-436) [Linux] MB_LEN_MAX incorrect

[ https://issues.apache.org/jira/browse/STDCXX-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Travis Vitek updated STDCXX-436: Attachment: LIMITS.cpp.patch Additional patch that appears to address the above mentioned issue. >

[jira] Updated: (STDCXX-436) [Linux] MB_LEN_MAX incorrect

[ https://issues.apache.org/jira/browse/STDCXX-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Travis Vitek updated STDCXX-436: Attachment: 18.limits.stdcxx-436.cpp The attached patch includes a regression test for this issue.

stdcxx atomics

I noticed that -- like other RW libs -- stdcxx does build the atomic ops sources even in ST builds although the logic in rw/_mutex.h picks up the vanilla implementation in 8-11 builds. Is this a mere slip? -- Your fault - core dumped.

[jira] Commented: (STDCXX-547) [Sun C++] 64-bit conversion warnings building the library

[ https://issues.apache.org/jira/browse/STDCXX-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526531 ] Farid Zaripov commented on STDCXX-547: -- Below is a warnings when building the library with ICC 10.0 / x64 platfo

[jira] Commented: (STDCXX-547) [Sun C++] 64-bit conversion warnings building the library

[ https://issues.apache.org/jira/browse/STDCXX-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526523 ] Farid Zaripov commented on STDCXX-547: -- The similar warnings got when building the library with MSVC 8.0 / x64 p

Re: [jira] Updated: (STDCXX-536) allow thread safety tests to time out without failing

Hi Travis, Can you describe how this all works? I.e., what happens to a test invoked without the --timeout option when it exceeds the default 295ms timeout? What happens to one that is invoked with the option? From your comment below it sounds like the solution you implemented is different from

RE: [jira] Closed: (STDCXX-517) No required options for generate.bat script

> -Original Message- > From: Eric Lemings [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 11, 2007 6:09 PM > To: stdcxx-dev@incubator.apache.org > Subject: RE: [jira] Closed: (STDCXX-517) No required options > for generate.bat script > > > Typo in README file: > > +

RE: [jira] Closed: (STDCXX-517) No required options for generate.bat script

Typo in README file: +specified a the suitable config file will be selected > -Original Message- > From: Farid Zaripov (JIRA) [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 11, 2007 8:31 AM > To: stdcxx-dev@incubator.apache.org > Subject: [jira] Closed: (STDCXX-51

[jira] Closed: (STDCXX-516) Rename generate.bat as configure.bat.

[ https://issues.apache.org/jira/browse/STDCXX-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farid Zaripov closed STDCXX-516. > Rename generate.bat as configure.bat. > - > > Key

[jira] Resolved: (STDCXX-516) Rename generate.bat as configure.bat.

[ https://issues.apache.org/jira/browse/STDCXX-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farid Zaripov resolved STDCXX-516. -- Resolution: Fixed Fixed thus: http://svn.apache.org/viewvc?rev=574618&view=rev > Rename genera

[jira] Resolved: (STDCXX-517) No required options for generate.bat script

[ https://issues.apache.org/jira/browse/STDCXX-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farid Zaripov resolved STDCXX-517. -- Resolution: Fixed Fixed thus: http://svn.apache.org/viewvc?rev=574613&view=rev > No required o

[jira] Closed: (STDCXX-517) No required options for generate.bat script

[ https://issues.apache.org/jira/browse/STDCXX-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farid Zaripov closed STDCXX-517. > No required options for generate.bat script > --- > >

[jira] Issue Comment Edited: (STDCXX-520) codecvt1.cpp example exits with exitcode=1

[ https://issues.apache.org/jira/browse/STDCXX-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526440 ] farid edited comment on STDCXX-520 at 9/11/07 5:14 AM: --- The example doesn't fail (crash

[jira] Updated: (STDCXX-520) codecvt1.cpp example exits with exitcode=1

[ https://issues.apache.org/jira/browse/STDCXX-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Farid Zaripov updated STDCXX-520: - Fix Version/s: (was: 4.2) 4.2.1 Issue Type: Improvement (was: Bug)