public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Use common_val_print in riscv-tdep.c
Date: Tue, 24 Mar 2020 08:24:11 -0400	[thread overview]
Message-ID: <040f66bd2d6aea4d35a2e5cb88b499799ee4c466@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 040f66bd2d6aea4d35a2e5cb88b499799ee4c466 ***

commit 040f66bd2d6aea4d35a2e5cb88b499799ee4c466
Author:     Tom Tromey <tom@tromey.com>
AuthorDate: Fri Mar 13 17:39:52 2020 -0600
Commit:     Tom Tromey <tom@tromey.com>
CommitDate: Fri Mar 13 18:03:39 2020 -0600

    Use common_val_print in riscv-tdep.c
    
    This changes some spots in riscv-tdep.c to use common_val_print rather
    than val_print.
    
    gdb/ChangeLog
    2020-03-13  Tom Tromey  <tom@tromey.com>
    
            * riscv-tdep.c (riscv_print_one_register_info): Use
            common_val_print.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 3cab13b743..21444545b4 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,8 @@
+2020-03-13  Tom Tromey  <tom@tromey.com>
+
+	* riscv-tdep.c (riscv_print_one_register_info): Use
+	common_val_print.
+
 2020-03-13  Tom Tromey  <tom@tromey.com>
 
 	* mi/mi-main.c (output_register): Use common_val_print.
diff --git a/gdb/riscv-tdep.c b/gdb/riscv-tdep.c
index 97741a32bd..2978b9e2d5 100644
--- a/gdb/riscv-tdep.c
+++ b/gdb/riscv-tdep.c
@@ -694,9 +694,7 @@ riscv_print_one_register_info (struct gdbarch *gdbarch,
       get_user_print_options (&opts);
       opts.deref_ref = 1;
 
-      val_print (regtype,
-		 value_embedded_offset (val), 0,
-		 file, 0, val, &opts, current_language);
+      common_val_print (val, file, 0, &opts, current_language);
 
       if (print_raw_format)
 	{
@@ -713,9 +711,7 @@ riscv_print_one_register_info (struct gdbarch *gdbarch,
       /* Print the register in hex.  */
       get_formatted_print_options (&opts, 'x');
       opts.deref_ref = 1;
-      val_print (regtype,
-		 value_embedded_offset (val), 0,
-		 file, 0, val, &opts, current_language);
+      common_val_print (val, file, 0, &opts, current_language);
 
       if (print_raw_format)
 	{
@@ -849,9 +845,7 @@ riscv_print_one_register_info (struct gdbarch *gdbarch,
 		  get_user_print_options (&opts);
 		  opts.deref_ref = 1;
 		  fprintf_filtered (file, "\t");
-		  val_print (regtype,
-			     value_embedded_offset (val), 0,
-			     file, 0, val, &opts, current_language);
+		  common_val_print (val, file, 0, &opts, current_language);
 		}
 	    }
 	}


             reply	other threads:[~2020-03-24 12:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 12:24 gdb-buildbot [this message]
2020-03-24 12:24 ` Failures on Fedora-x86_64-cc-with-index, branch master gdb-buildbot
2020-03-24 12:31 ` Failures on Fedora-i686, " gdb-buildbot
2020-03-24 13:17 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2020-03-24 13:37 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2020-03-24 14:13 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2020-03-27 11:36 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
2020-03-27 19:51 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2020-03-28  1:01 ` Failures on Ubuntu-Aarch64-m64, " gdb-buildbot
2020-03-28  1:35 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot

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=040f66bd2d6aea4d35a2e5cb88b499799ee4c466@gdb-build \
    --to=gdb-buildbot@sergiodj.net \
    --cc=gdb-testers@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).