From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org
Subject: Make bfd_byte an int8_t, flagword a uint32_t
Date: Fri, 28 Apr 2023 15:44:51 +0930 [thread overview]
Message-ID: <ZEtkW7ozVq5sX1e8@squeak.grove.modra.org> (raw)
* bfd-in.h (bfd_byte): Typedef as int8_t.
(flagword): Typedef as uint32_t.
(bfd_vma, bfd_signed_vma, bfd_size_type, symvalue): Use stdint
types in !BFD64 case.
* bfd-in2.h: Regenerate.
---
bfd/bfd-in.h | 12 ++++++------
bfd/bfd-in2.h | 12 ++++++------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/bfd/bfd-in.h b/bfd/bfd-in.h
index c3f92c142a5..eb6ee9cf816 100644
--- a/bfd/bfd-in.h
+++ b/bfd/bfd-in.h
@@ -115,10 +115,10 @@ typedef uint64_t symvalue;
#else /* not BFD64 */
-typedef unsigned long bfd_vma;
-typedef long bfd_signed_vma;
-typedef unsigned long symvalue;
-typedef unsigned long bfd_size_type;
+typedef uint32_t bfd_vma;
+typedef int32_t bfd_signed_vma;
+typedef uint32_t bfd_size_type;
+typedef uint32_t symvalue;
#endif /* not BFD64 */
@@ -135,8 +135,8 @@ extern void bfd_fprintf_vma (bfd *, void *, bfd_vma);
#define bfd_printf_vma(abfd,x) bfd_fprintf_vma (abfd,stdout,x)
-typedef unsigned int flagword; /* 32 bits of flags */
-typedef unsigned char bfd_byte;
+typedef uint32_t flagword; /* 32 bits of flags */
+typedef uint8_t bfd_byte;
\f
/* File formats. */
diff --git a/bfd/bfd-in2.h b/bfd/bfd-in2.h
index a04e97eda67..fcfd22662f3 100644
--- a/bfd/bfd-in2.h
+++ b/bfd/bfd-in2.h
@@ -122,10 +122,10 @@ typedef uint64_t symvalue;
#else /* not BFD64 */
-typedef unsigned long bfd_vma;
-typedef long bfd_signed_vma;
-typedef unsigned long symvalue;
-typedef unsigned long bfd_size_type;
+typedef uint32_t bfd_vma;
+typedef int32_t bfd_signed_vma;
+typedef uint32_t bfd_size_type;
+typedef uint32_t symvalue;
#endif /* not BFD64 */
@@ -142,8 +142,8 @@ extern void bfd_fprintf_vma (bfd *, void *, bfd_vma);
#define bfd_printf_vma(abfd,x) bfd_fprintf_vma (abfd,stdout,x)
-typedef unsigned int flagword; /* 32 bits of flags */
-typedef unsigned char bfd_byte;
+typedef uint32_t flagword; /* 32 bits of flags */
+typedef uint8_t bfd_byte;
\f
/* File formats. */
--
Alan Modra
Australia Development Lab, IBM
reply other threads:[~2023-04-28 6:14 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=ZEtkW7ozVq5sX1e8@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@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).