Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org,
	Joel Brobecker <brobecker@adacore.com>,
	Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: [FYI] Use pulongest in aarch64-linux-tdep.c
Date: Thu, 06 Sep 2018 04:17:00 -0000	[thread overview]
Message-ID: <87o9dbuuo8.fsf@redhat.com> (raw)
In-Reply-To: <20180815160724.11227-1-tom@tromey.com> (Tom Tromey's message of	"Wed, 15 Aug 2018 10:07:24 -0600")

On Wednesday, August 15 2018, Tom Tromey wrote:

> While testing a patch on the buildbot, I got this error:
>
> ../../binutils-gdb/gdb/aarch64-linux-tdep.c: In function uint64_t aarch64_linux_core_read_vq(gdbarch*, bfd*):
> ../../binutils-gdb/gdb/aarch64-linux-tdep.c:285:29: error: format %ld expects argument of type long int, but argument 2 has type uint64_t {aka long long unsigned int} [-Werror=format=]
>
> This patch avoids the problem by using pulongest rather than %ld.
> This seems safe to me because, if aarch64-linux-tdep.c is included in
> the build, then ULONGEST must be a 64-bit type.

Hi Tom,

It seems like this commit should have been applied to the 8.2 branch,
but wasn't.  GDB 8.2 was released without it, and it breaks to build on
i686 and armvhl, as can be seen here:

  https://koji.fedoraproject.org/koji/taskinfo?taskID=29499845

I'll backport the commit locally and rebuild it, but I thought it'd be
good to mention publicly in case anyone else is seeing these failures.

Cheers,

> gdb/ChangeLog
> 2018-08-15  Tom Tromey  <tom@tromey.com>
>
> 	* aarch64-linux-tdep.c (aarch64_linux_core_read_vq): Use pulongest.
> ---
>  gdb/ChangeLog            | 4 ++++
>  gdb/aarch64-linux-tdep.c | 5 +++--
>  2 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/gdb/ChangeLog b/gdb/ChangeLog
> index d16920d80e9..9fac8ccf5f4 100644
> --- a/gdb/ChangeLog
> +++ b/gdb/ChangeLog
> @@ -1,3 +1,7 @@
> +2018-08-15  Tom Tromey  <tom@tromey.com>
> +
> +	* aarch64-linux-tdep.c (aarch64_linux_core_read_vq): Use pulongest.
> +
>  2018-08-14  Jan Vrany  <jan.vrany@fit.cvut.cz>
>  
>  	* mi/mi-cmd-disas.c (mi_cmd_disassemble): Add -a option.
> diff --git a/gdb/aarch64-linux-tdep.c b/gdb/aarch64-linux-tdep.c
> index 99e6a1590b8..389f4f494ec 100644
> --- a/gdb/aarch64-linux-tdep.c
> +++ b/gdb/aarch64-linux-tdep.c
> @@ -282,12 +282,13 @@ aarch64_linux_core_read_vq (struct gdbarch *gdbarch, bfd *abfd)
>    if (vq > AARCH64_MAX_SVE_VQ)
>      {
>        warning (_("SVE Vector length in core file not supported by this version"
> -		 " of GDB.  (VQ=%ld)"), vq);
> +		 " of GDB.  (VQ=%s)"), pulongest (vq));
>        return 0;
>      }
>    else if (vq == 0)
>      {
> -      warning (_("SVE Vector length in core file is invalid. (VQ=%ld"), vq);
> +      warning (_("SVE Vector length in core file is invalid. (VQ=%s"),
> +	       pulongest (vq));
>        return 0;
>      }
>  
> -- 
> 2.17.1

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  reply	other threads:[~2018-09-06  4:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15 16:08 Tom Tromey
2018-09-06  4:17 ` Sergio Durigan Junior [this message]
2018-09-06  4:43   ` Tom Tromey
2018-10-03  1:31 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=87o9dbuuo8.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=tom@tromey.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