public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Walfred Tedeschi <walfred.tedeschi@intel.com>
To: gdb-patches@sourceware.org
Cc: Walfred Tedeschi <walfred.tedeschi@intel.com>
Subject: [OB PATCH] Fix ARI new warnings introduced in i386-tdep.c.
Date: Thu, 11 Jun 2015 11:46:00 -0000	[thread overview]
Message-ID: <1434023186-12251-1-git-send-email-walfred.tedeschi@intel.com> (raw)

1. gdb/i386-tdep.c:8720: Do not use 'long long', instead use LONGEST
gdb/i386-tdep.c:8720:  long long int size;

2. gdb/i386-tdep.c:8755: Do not use printf(%ll), instead use printf(%s,phex()) to dump a 'long long' value
gdb/i386-tdep.c:8755: ui_out_field_fmt (uiout, "size", "%lld", size);

2015-06-11  Walfred Tedeschi  <walfred.tedeschi@intel.com>

	* i386-tdep.c (i386_mpx_print_bounds): use of LONGEST instead of
	long long int and plongest instead of %ll.

---
 gdb/i386-tdep.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gdb/i386-tdep.c b/gdb/i386-tdep.c
index 6304591..133021f 100644
--- a/gdb/i386-tdep.c
+++ b/gdb/i386-tdep.c
@@ -8717,7 +8717,7 @@ static void
 i386_mpx_print_bounds (const CORE_ADDR bt_entry[4])
 {
   struct ui_out *uiout = current_uiout;
-  long long int size;
+  LONGEST size;
   struct gdbarch *gdbarch = get_current_arch ();
   CORE_ADDR onecompl = ~((CORE_ADDR) 0);
   int bounds_in_map = ((~bt_entry[1] == 0 && bt_entry[0] == onecompl) ? 1 : 0);
@@ -8752,7 +8752,7 @@ i386_mpx_print_bounds (const CORE_ADDR bt_entry[4])
 
       size = (size > -1 ? size + 1 : size);
       ui_out_text (uiout, ", size = ");
-      ui_out_field_fmt (uiout, "size", "%lld", size);
+      ui_out_field_fmt (uiout, "size", "%s", plongest (size));
 
       ui_out_text (uiout, ", metadata = ");
       ui_out_field_core_addr (uiout, "metadata", gdbarch, bt_entry[3]);
-- 
2.1.4

                 reply	other threads:[~2015-06-11 11:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1434023186-12251-1-git-send-email-walfred.tedeschi@intel.com \
    --to=walfred.tedeschi@intel.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).