public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org To: bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gdr@nerim.net, jkanze@caicheuvreux.com, nobody@gcc.gnu.org Subject: Re: libstdc++/8230: Buggy allocator behaviour Date: Wed, 20 Nov 2002 05:07:00 -0000 [thread overview] Message-ID: <20021113221911.21632.qmail@sources.redhat.com> (raw) Synopsis: Buggy allocator behaviour Responsible-Changed-From-To: unassigned->bkoz Responsible-Changed-By: bkoz Responsible-Changed-When: Wed Nov 13 14:19:11 2002 Responsible-Changed-Why: Mine. State-Changed-From-To: open->feedback State-Changed-By: bkoz State-Changed-When: Wed Nov 13 14:19:11 2002 State-Changed-Why: I don't think this is an allocator::allocate issue per se. The member function reserve is only in std::vector and std::vector<bool>, and the standard says 23.2.4.2 - vector capacity -4- Throws: length_error if n > max_size().* Where allocator::allocate doesn't know what vector::max_size is. This fix brings the code up to conformance, and is the best fix I think. -benjamin http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8230
next reply other threads:[~2002-11-13 22:19 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-20 5:07 bkoz [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-23 1:16 bkoz 2002-11-21 14:01 Richard Henderson 2002-11-21 4:06 Gabriel Dos Reis 2002-11-21 3:47 Matt Austern 2002-11-20 23:03 Gabriel Dos Reis 2002-11-20 19:09 Gabriel Dos Reis 2002-11-20 18:20 Benjamin Kosnik 2002-11-20 18:19 Benjamin Kosnik 2002-11-20 18:02 Gabriel Dos Reis 2002-10-15 5:56 gdr
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=20021113221911.21632.qmail@sources.redhat.com \ --to=bkoz@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=gdr@nerim.net \ --cc=jkanze@caicheuvreux.com \ --cc=nobody@gcc.gnu.org \ /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: linkBe 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).