From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Allow cast of 128-bit integer to pointer
Date: Fri, 08 Dec 2023 08:15:43 -0700 [thread overview]
Message-ID: <87bkb0iv34.fsf@tromey.com> (raw)
In-Reply-To: <20231125022548.1613394-1-tom@tromey.com> (Tom Tromey's message of "Fri, 24 Nov 2023 19:25:48 -0700")
>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
Tom> PR rust/31082 points out that casting a 128-bit integer to a pointer
Tom> will fail. This happens because a case in value_cast was not
Tom> converted to use GMP.
Tom> This patch fixes the problem. I am not really sure that testing
Tom> against the negative value here makes sense, but I opted to just
Tom> preserve the existing behavior rather than change it.
I'm checking this in.
Tom
prev parent reply other threads:[~2023-12-08 15:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 2:25 Tom Tromey
2023-12-08 15:15 ` Tom Tromey [this message]
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=87bkb0iv34.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.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: 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).