public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH] Allow cast of 128-bit integer to pointer
Date: Fri, 24 Nov 2023 19:25:48 -0700	[thread overview]
Message-ID: <20231125022548.1613394-1-tom@tromey.com> (raw)

PR rust/31082 points out that casting a 128-bit integer to a pointer
will fail.  This happens because a case in value_cast was not
converted to use GMP.

This patch fixes the problem.  I am not really sure that testing
against the negative value here makes sense, but I opted to just
preserve the existing behavior rather than change it.

Regression tested on x86-64 Fedora 38.

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31082
---
 gdb/gmp-utils.h                 | 15 ++++++++++++++-
 gdb/testsuite/gdb.rust/expr.exp |  5 +++++
 gdb/valops.c                    | 14 ++++++--------
 3 files changed, 25 insertions(+), 9 deletions(-)

diff --git a/gdb/gmp-utils.h b/gdb/gmp-utils.h
index a5c27feb59f..52052e30d26 100644
--- a/gdb/gmp-utils.h
+++ b/gdb/gmp-utils.h
@@ -251,19 +251,32 @@ struct gdb_mpz
     return result;
   }
 
+  gdb_mpz operator- () const
+  {
+    gdb_mpz result;
+    mpz_neg (result.m_val, m_val);
+    return result;
+  }
+
   gdb_mpz &operator<<= (unsigned long nbits)
   {
     mpz_mul_2exp (m_val, m_val, nbits);
     return *this;
   }
 
-  gdb_mpz operator<< (unsigned long nbits) const
+  gdb_mpz operator<< (unsigned long nbits) const &
   {
     gdb_mpz result;
     mpz_mul_2exp (result.m_val, m_val, nbits);
     return result;
   }
 
+  gdb_mpz operator<< (unsigned long nbits) &&
+  {
+    mpz_mul_2exp (m_val, m_val, nbits);
+    return *this;
+  }
+
   gdb_mpz operator>> (unsigned long nbits) const
   {
     gdb_mpz result;
diff --git a/gdb/testsuite/gdb.rust/expr.exp b/gdb/testsuite/gdb.rust/expr.exp
index ce2cce2677c..cec3c1fccd8 100644
--- a/gdb/testsuite/gdb.rust/expr.exp
+++ b/gdb/testsuite/gdb.rust/expr.exp
@@ -169,3 +169,8 @@ gdb_test "with debug expression 1 -- print \"foo\"" \
 	 " Constant: 0" \
 	 "evaluation of this expression requires the target program to be active"] \
     "print a string with expression debug turned on"
+
+# PR rust/31082 - truncating to a pointer would fail.  Depending on
+# the default host architecture, this may or may not print a warning.
+gdb_test "print (0xffffffd00000009a as *mut u64)" \
+    "(warning: value truncated\[\r\n\]+)?.* = \\(\\*mut u64\\) $hex"
diff --git a/gdb/valops.c b/gdb/valops.c
index a8760ccf3e4..bf376921ca3 100644
--- a/gdb/valops.c
+++ b/gdb/valops.c
@@ -603,15 +603,13 @@ value_cast (struct type *type, struct value *arg2)
 	 pointers and four byte addresses.  */
 
       int addr_bit = gdbarch_addr_bit (type2->arch ());
-      LONGEST longest = value_as_long (arg2);
+      gdb_mpz longest = value_as_mpz (arg2);
 
-      if (addr_bit < sizeof (LONGEST) * HOST_CHAR_BIT)
-	{
-	  if (longest >= ((LONGEST) 1 << addr_bit)
-	      || longest <= -((LONGEST) 1 << addr_bit))
-	    warning (_("value truncated"));
-	}
-      return value_from_longest (to_type, longest);
+      gdb_mpz addr_val = gdb_mpz (1) << addr_bit;
+      if (longest >= addr_val || longest <= -addr_val)
+	warning (_("value truncated"));
+
+      return value_from_mpz (to_type, longest);
     }
   else if (code1 == TYPE_CODE_METHODPTR && code2 == TYPE_CODE_INT
 	   && value_as_long (arg2) == 0)
-- 
2.41.0


             reply	other threads:[~2023-11-25  2:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-25  2:25 Tom Tromey [this message]
2023-12-08 15:15 ` Tom Tromey

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=20231125022548.1613394-1-tom@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).