From: David Edelsohn <dje.gcc@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>,
Paolo Carlini <paolo.carlini@oracle.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] 21_strings/basic_string/capacity/wchar_t/18654.cc
Date: Fri, 13 Nov 2015 23:53:00 -0000 [thread overview]
Message-ID: <CAGWvny=uVdMcSNJ9mYo+haM-gD4aCZ8z7g4Q7nP=s7TLxBg4+Q@mail.gmail.com> (raw)
In-Reply-To: <CAGWvnynw3zVbZw0hFWR_UqEt4bMmyTvfPua+mEPxnVRXiD1msw@mail.gmail.com>
On Fri, Nov 13, 2015 at 1:40 PM, David Edelsohn <dje.gcc@gmail.com> wrote:
> http://www.cplusplus.com/reference/string/basic_string/reserve/
>
> "Note that the resulting string capacity may be equal or greater than n."
>
> The current testcase verifies that the capacity is exactly equal to
> the length of the string or reserve value, but the standard allows the
> capacity to be larger. On AIX, the capacity is larger and the
> testcase incorrectly fails.
>
> Linux x86-64:
> i: 4
> str.length: 4
> str.capacity: 4
> str.capacity: 12
> str.capacity: 8
> str.capacity: 4
>
> AIX:
> i: 4
> str.length: 4
> str.capacity: 7 <-- i
> str.capacity: 14 <-- i*3
> str.capacity: 8 <-- i*2
> str.capacity: 7 <-- default
>
> * 21_strings/basic_string/capacity/wchar_t/18654.cc: Verify the
Jonathan,
AIX has 2-byte wchar_t in 32 bit mode, which seems to be the cause of
all of the libstdc++ testsuite wchar_t failures. If GCC libstdc++ is
suppose to shrink-to-fit, how should the testcases be fixed?
Thanks, David
next prev parent reply other threads:[~2015-11-13 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 18:41 David Edelsohn
2015-11-13 23:53 ` David Edelsohn [this message]
2015-11-14 0:56 ` Jonathan Wakely
2015-11-14 17:25 ` Jonathan Wakely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGWvny=uVdMcSNJ9mYo+haM-gD4aCZ8z7g4Q7nP=s7TLxBg4+Q@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=paolo.carlini@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).