Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: riscv-tdep.c in 32-bits build
Date: Fri, 21 Dec 2018 00:57:00 -0000	[thread overview]
Message-ID: <20181221005727.GF3456@embecosm.com> (raw)
In-Reply-To: <6948b903-63f2-b0d2-4f66-738b95b51385@ericsson.com>

* Simon Marchi <simon.marchi@ericsson.com> [2018-12-20 17:26:01 +0000]:

> Hi Andrew,
> 
> I just noticed this error when building for i386-linux-gnu.
> 
>   CXX    riscv-tdep.o
> /home/emaisin/src/binutils-gdb/gdb/riscv-tdep.c: In function ‘CORE_ADDR riscv_scan_prologue(gdbarch*, CORE_ADDR, CORE_ADDR, riscv_unwind_cache*)’:
> /home/emaisin/src/binutils-gdb/gdb/riscv-tdep.c:1548:43: error: format ‘%ld’ expects argument of type ‘long int’, but argument 4 has type ‘CORE_ADDR {aka long long unsigned int}’ [-Werror=format=]
>                                      offset);
>                                            ^
> I looked at it a bit and decided to let you choose how you wanted to fix
> it.  Since this is a CORE_ADDR, I first thought we should call paddress.
> But this variable represents an offset, not an absolute address, so I am
> not sure if paddress is really appropriate.

Thanks for the report.  The use of CORE_ADDR is not ideal, that's just
what the existing API into pv_area uses.  Given it's an offset,
possibly LONGEST would be more appropriate?

Anyway, I propose casting to LONGEST and printing that.  Unless you
object I'll push this in a few days.

Thanks,
Andrew

--

gdb/riscv: Format CORE_ADDR as a string for printing

Avoid compiler errors caused by trying to print CORE_ADDR using '%ld'
format, instead convert to a string and print that instead.

gdb/ChangeLog:

	* riscv-tdep.c (riscv_scan_prologue): Use plongest to format
	offset as a string.
---
 gdb/ChangeLog    | 5 +++++
 gdb/riscv-tdep.c | 4 ++--
 2 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/gdb/riscv-tdep.c b/gdb/riscv-tdep.c
index 88b79af866f..464021f664c 100644
--- a/gdb/riscv-tdep.c
+++ b/gdb/riscv-tdep.c
@@ -1543,9 +1543,9 @@ riscv_scan_prologue (struct gdbarch *gdbarch,
             {
               if (riscv_debug_unwinder)
                 fprintf_unfiltered (gdb_stdlog,
-                                    "Register $%s at stack offset %ld\n",
+                                    "Register $%s at stack offset %s\n",
                                     gdbarch_register_name (gdbarch, i),
-                                    offset);
+                                    plongest ((LONGEST) offset));
               trad_frame_set_addr (cache->regs, i, offset);
             }
 	}
-- 
2.14.5


  reply	other threads:[~2018-12-21  0:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20 17:26 Simon Marchi
2018-12-21  0:57 ` Andrew Burgess [this message]
2018-12-21 15:22   ` 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=20181221005727.GF3456@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.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