bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/29348] gdb/build: format specifies type 'unsigned long' bu


From: cvs-commit at gcc dot gnu.org
Subject: [Bug binutils/29348] gdb/build: format specifies type 'unsigned long' but the argument has type 'bfd_size_type' (aka 'unsigned long long')
Date: Mon, 01 Aug 2022 01:08:51 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=29348

--- Comment #15 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot 
gnu.org> ---
The binutils-2_39-branch branch has been updated by Alan Modra
<amodra@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b336123a087f9a85e7b24d7e420bd44b9c9d3552

commit b336123a087f9a85e7b24d7e420bd44b9c9d3552
Author: Alan Modra <amodra@gmail.com>
Date:   Sun Jul 31 19:25:32 2022 +0930

    PR29348, BFD_VMA_FMT wrong

    There is a problem with my commit 0e3c1eebb2, which replaced
    bfd_uint64_t with uint64_t: Some hosts typedef int64_t to long long
    even when long is the same size as long long.  That confuses the code
    choosing one of "l", "ll", or "I64" for BFD_VMA_FMT, and results in
    warnings.

    Write a direct configure test for the printf int64_t style instead.
    This removes the last use of BFD_HOST_64BIT_LONG, so delete that.
    Note that the changes to configure.com are pure guesswork.

            PR 29348
            * bfd-in.h (BFD_HOST_64BIT_LONG): Don't define.
            (BFD_VMA_FMT): Define using BFD_INT64_FMT when 64-bit.
            (bfd_vma, bfd_signed_vma): Move comments to 64-bit typedefs.
            * configure.ac (BFD_HOST_64BIT_LONG): Delete.
            (BFD_INT64_FMT): New config test.
            * configure.com: Update similarly.
            * Makefile.in: Regenerate.
            * bfd-in2.h: Regenerate.
            * configure: Regenerate.

    (cherry picked from commit 1a5178fe284547ef2abd8ae66588c9999d61c524)

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]