diff options
| author | Alan Modra <amodra@gmail.com> | 2022-07-31 19:25:32 +0930 |
|---|---|---|
| committer | Alan Modra <amodra@gmail.com> | 2022-08-01 09:30:33 +0930 |
| commit | 1a5178fe284547ef2abd8ae66588c9999d61c524 (patch) | |
| tree | a3e10f649adb19dfc046d345a73ecf2f1befdc3f /bfd/Makefile.in | |
| parent | df0e73ff9307251d179aa4158347deccc9576b85 (diff) | |
| download | binutils-1a5178fe284547ef2abd8ae66588c9999d61c524.zip binutils-1a5178fe284547ef2abd8ae66588c9999d61c524.tar.gz binutils-1a5178fe284547ef2abd8ae66588c9999d61c524.tar.bz2 | |
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.
Diffstat (limited to 'bfd/Makefile.in')
| -rw-r--r-- | bfd/Makefile.in | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bfd/Makefile.in b/bfd/Makefile.in index d3ef4c2..a26f74d 100644 --- a/bfd/Makefile.in +++ b/bfd/Makefile.in @@ -330,7 +330,7 @@ AUTOCONF = @AUTOCONF@ AUTOHEADER = @AUTOHEADER@ AUTOMAKE = @AUTOMAKE@ AWK = @AWK@ -BFD_HOST_64BIT_LONG = @BFD_HOST_64BIT_LONG@ +BFD_INT64_FMT = @BFD_INT64_FMT@ CATALOGS = @CATALOGS@ CATOBJEXT = @CATOBJEXT@ CC = @CC@ |