I'm voting to keeping this project active.
Scott
-Original Message-
From: William A. Rowe Jr. [mailto:wr...@rowe-clan.net]
Sent: Thursday, February 02, 2012 9:04 AM
To: dev@stdcxx.apache.org
Subject: [VOTE] Retirement of stdcxx to the 'Attic'?
Fans and contributors,
it appears that
I think I'll use this email [EMAIL PROTECTED]
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2008 10:58 PM
To: dev@stdcxx.apache.org
Subject: Re: [PATCH] STDCXX-401 test suite should honor TMPDIR
Scott Zhong wrote:
Changelog
, 2008 4:19 PM
To: dev@stdcxx.apache.org
Subject: Re: [PATCH] STDCXX-1019 __rw_mkstemp in file.cpp should honor
TMPDIR environment variable
Scott Zhong wrote:
Fix to fnamebuf array size and invoke getenv only once.
The fix looks good to me but I'm having trouble applying the patch.
You
Hi Farid, thanks for the quick response, here is the new version with
the changes suggested.
Index: tests/src/file.cpp
===
--- tests/src/file.cpp (revision 702657)
+++ tests/src/file.cpp (working copy)
@@ -208,8 +208,13 @@
#ifndef
-tmp, strerror (errno));
}
# else
-Original Message-
From: Scott Zhong [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2008 9:25 AM
To: dev@stdcxx.apache.org
Subject: RE: [PATCH] STDCXX-401 test suite should honor TMPDIR
Hi Farid, thanks for the quick response, here
-Original Message-
From: Scott Zhong [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 09, 2008 9:31 AM
To: dev@stdcxx.apache.org
Subject: RE: [PATCH] STDCXX-401 test suite should honor TMPDIR
That const_cast isn't suppose to be there. Here is the correct
version:
Index: tests/src
-
From: Scott Zhong [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 08, 2008 11:03 AM
To: dev@stdcxx.apache.org
Subject: RE: [PATCH] STDCXX-1019 __rw_mkstemp in file.cpp should honor
TMPDIR environment variable
Posted wrong diff. here is the correct diff
Index: src/file.cpp
https://issues.apache.org/jira/browse/STDCXX-1020
Index: util/memchk.cpp
===
--- util/memchk.cpp (revision 702657)
+++ util/memchk.cpp (working copy)
@@ -116,9 +116,11 @@
// operation away (as SunOS does, for
That's incorrect; all the runs have been running just that the stdcxx
results web page hasn't been updated yet. We'll have to wait for the
next nightly builds to finish in order for the stdcxx result web page to
update.
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED]
http://svn.apache.org/repos/asf/stdcxx/branches/4.2.x not changed since
694682
stdcxx 4.2.x nightly builds only occur when a change has occurred over
the last run.
Scott Z.
-Original Message-
From: Farid Zaripov [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 17, 2008 7:23 AM
It could also be that Martin is out until mid next week and the scripts
that generate the build page haven't been run yet.
Scott Z.
-Original Message-
From: Scott Zhong [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 17, 2008 8:25 AM
To: dev@stdcxx.apache.org
Subject: RE
Martin, do I need to switch to the new tags to do nightly testing?
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED] On Behalf Of Martin Sebor
Sent: Thursday, April 10, 2008 4:30 PM
To: dev@stdcxx.apache.org
Subject: tags/4.2.1-rc-1 results
Nightly build results for
Changes made:
* fix a bug (not filed) that would potentially access an array using
negative index
* add function compute_type_bits to calculate the number of bits in the
value representation of type T.
* add a check that would only define exact width integer type if the
system supports two's
Some platforms are going to show up as ERROR / DATA today and tomorrow
due to code changes in the infrastructure. This issue is being looked
at and hopefully be fix by today.
and that it uses
a two's complement representation?
A few more comments are inline...
Scott Zhong wrote:
Index: LIMITS.cpp
===
--- LIMITS.cpp (revision 638996)
+++ LIMITS.cpp (working copy)
@@ -223,7 +223,19 @@
return
No, not currently, it is within the function that saves the log that
throw an exception.
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 01, 2008 10:06 AM
To: dev@stdcxx.apache.org
Subject: Re: [aCC 6.05] too many warnings
Scott Zhong wrote
OS: win_xp-2-x86 compiler: icl-9.1
The reason for this failure is because of the windows nightly build
machine failure.
OS: all windowscompiler: MSVC-9.0
The reason for this failure is the scripts used to parse the results are
parsing incorrectly. This issue is being looked at and will
cat /build/scottz/t2.cpp aCC -V aCC -c +w /build/scottz/t2.cpp
#include cstdlib
int main()
{
static char * test = 0;
if (!test) {
test = (char *)std::malloc (12345);
*test = '\0';
}
return 0;
}
aCC: HP C/aC++ B3910B A.06.16 [Nov 26 2007]
/build/scottz/t2.cpp, line 8,
to allocate memory. The warning could be clearer about
it.
Martin
Scott Zhong wrote:
cat /build/scottz/t2.cpp aCC -V aCC -c +w
/build/scottz/t2.cpp
#include cstdlib
int main()
{
static char * test = 0;
if (!test) {
test = (char *)std::malloc (12345);
*test
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2008 12:32 PM
To: dev@stdcxx.apache.org
Subject: RE: [PATCH] STDCXX-423
Okay, so this function seems to correctly compute the number of bytes
in the value representation of the object.
http://issues.apache.org/jira/browse/STDCXX-401
Title: test suite should honor TMPDIR
stdcxx-401 patch part 1 is in
http://mail-archives.apache.org/mod_mbox/stdcxx-dev/200803.mbox/%3cCFFDD
[EMAIL PROTECTED]
stdcxx-401 patch part 2 affects:
./src/file.cpp
./util/memchk.cpp
./bin/xbuildgen
-Original Message-
From: Martin Sebor [mailto:[EMAIL PROTECTED] On Behalf Of Martin Sebor
Sent: Monday, March 10, 2008 3:39 PM
To: dev@stdcxx.apache.org
Subject: Re: STDCXX-401
Thanks for the patch, Scott! I think this a start, but suspect
there are a few other places in the
Split _mutex.h into
_mutex-aix.h
_mutex-deccxx.h
_mutex.h
_mutex-i386gcc.h
_mutex-ia64-x86-64.h
_mutex-parisc.h
_mutex-sgi.h
_mutex-sparc.h
http://www.fileden.com/files/2008/1/30/1729926/patch.stdcxx-563.tar
--- LIMITS.cpp (revision 624452)
+++ LIMITS.cpp (working copy)
@@ -223,13 +223,27 @@
return bits;
}
+template class T
+unsigned compute_byte_size()
+{
+T max = T (one);
+unsigned byte = 1;
+for (int i = 1; T (max * two) max; max *= two, i++) {
+if (i 8 ) {byte++; i
Hi All,
I had finally found the source of the link warnings: it is occurring
because in the linker we use relative path in the library lookup -L
relative path which confuses the linker as to which stdcxx library to
use. This is because the compiler comes with a version of the stdcxx
library:
-
+addr = (char*)(void*)(0x0 - sizeof(size_t));
}
return addr;
-Original Message-
From: Scott Zhong [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 29, 2008 2:49 PM
To: dev@stdcxx.apache.org
Subject: RE: [PATCH] STDCXX-705
I tried to access the red zone and a seg
Subject: Re: [PATCH] STDCXX-705
Scott Zhong wrote:
Could
addr = (char*)(void*)size_t(-1);
Be a better choice for a bad address?
I'm not sure.
The weird looking expression in the function tries to compute
an address that's beyond the last text segment page, or 16MB
past the address
27 matches
Mail list logo
