From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA 2/5] Let print_decimal_chars handle signed values
Date: Mon, 05 Jun 2017 19:38:00 -0000 [thread overview]
Message-ID: <87wp8q5ip6.fsf@pokyo> (raw)
In-Reply-To: <3a7c7f3e-6e5a-55d0-9d0a-978b382f9cc4@redhat.com> (Pedro Alves's message of "Mon, 5 Jun 2017 18:22:12 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> On 06/02/2017 08:36 PM, Tom Tromey wrote:
>> + out_vec->reserve (len);
Pedro> std::vector::reserve() != std::vector::resize() ...
Yikes, sorry about that.
Maybe a buildbot instance could be set up to use libstdc++ debug mode
and ASAN? That would help avoid this kind of error.
Tom
next prev parent reply other threads:[~2017-06-05 19:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 19:36 [RFA 0/5] improve printing of 128 bit ints Tom Tromey
2017-06-02 19:37 ` [RFA 3/5] Simplify print_scalar_formatted Tom Tromey
2017-06-05 17:27 ` Pedro Alves
2017-06-02 19:37 ` [RFA 4/5] Remove val_print_type_code_int Tom Tromey
2017-06-02 19:37 ` [RFA 1/5] Don't always zero pad in print_*_chars Tom Tromey
2017-06-05 17:27 ` Pedro Alves
2017-06-02 19:37 ` [RFA 5/5] Add some 128-bit integer tests Tom Tromey
2017-06-05 17:33 ` Pedro Alves
2017-06-02 19:37 ` [RFA 2/5] Let print_decimal_chars handle signed values Tom Tromey
2017-06-05 17:22 ` Pedro Alves
2017-06-05 19:38 ` Tom Tromey [this message]
2017-06-05 17:35 ` [RFA 0/5] improve printing of 128 bit ints Pedro Alves
2017-06-08 14:32 ` Tom Tromey
2017-06-08 16:12 ` Power/AltiVec question (Re: [RFA 0/5] improve printing of 128 bit ints) Pedro Alves
2017-06-12 14:34 ` Tom Tromey
2017-06-12 18:26 ` Pedro Alves
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=87wp8q5ip6.fsf@pokyo \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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).