From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA 0/5] improve printing of 128 bit ints
Date: Mon, 05 Jun 2017 17:35:00 -0000 [thread overview]
Message-ID: <e40c6eb5-afa3-5fab-42b4-76867e1ed0f6@redhat.com> (raw)
In-Reply-To: <20170602193651.3173-1-tom@tromey.com>
On 06/02/2017 08:36 PM, Tom Tromey wrote:
> I wanted to improve 128-bit integer support, primarily for Rust,
> though I see in Bugzilla that I reported this bug at least twice for C
> as well.
>
> Full 128 bit integer support has two main aspects: printing and
> arithmetic (including parser support). This series cleans up
> printing, (bug 16225); leaving arithmetic for a future bug (bug
> 20991).
>
> Previous printing was implemented, but always zero-padded and did not
> correctly handle signed values. This series fixes that and removes
> some redundant code as well.
>
> Regtested on the buildbot.
For some reason, I don't have a copy of patch #4. But I read it
via the list archive, and it looks good to me.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-06-05 17:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 19:36 Tom Tromey
2017-06-02 19:37 ` [RFA 4/5] Remove val_print_type_code_int 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 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
2017-06-05 17:35 ` Pedro Alves [this message]
2017-06-08 14:32 ` [RFA 0/5] improve printing of 128 bit ints 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=e40c6eb5-afa3-5fab-42b4-76867e1ed0f6@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).