From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org
Subject: Don't define COFF_MAGIC
Date: Tue, 30 May 2023 13:52:23 +0930 [thread overview]
Message-ID: <ZHV5/28XpXf2d9Wd@squeak.grove.modra.org> (raw)
This macro was unused apart from aout/encap.h, which has been deleted.
* config/tc-arm.h (COFF_MAGIC): Don't define.
* config/tc-sh.h (COFF_MAGIC): Don't define.
* config/tc-z80.h (COFF_MAGIC): Don't define.
* config/tc-z8k.h (COFF_MAGIC): Don't define.
diff --git a/gas/config/tc-arm.h b/gas/config/tc-arm.h
index 95fe5255746..9d6b303842b 100644
--- a/gas/config/tc-arm.h
+++ b/gas/config/tc-arm.h
@@ -28,7 +28,6 @@
#define WORKING_DOT_WORD
-#define COFF_MAGIC ARMMAGIC
#define TARGET_ARCH bfd_arch_arm
#define DIFF_EXPR_OK
diff --git a/gas/config/tc-sh.h b/gas/config/tc-sh.h
index 23875ab1ad1..b157bd4dab9 100644
--- a/gas/config/tc-sh.h
+++ b/gas/config/tc-sh.h
@@ -130,8 +130,6 @@ extern void sh_frob_file (void);
#ifdef OBJ_COFF
/* COFF specific definitions. */
-#define COFF_MAGIC (!target_big_endian ? SH_ARCH_MAGIC_LITTLE : SH_ARCH_MAGIC_BIG)
-
#define tc_coff_symbol_emit_hook(a) ; /* Not used. */
#define TC_KEEP_FX_OFFSET 1
diff --git a/gas/config/tc-z80.h b/gas/config/tc-z80.h
index ef17ccecc70..c86a1ea10ff 100644
--- a/gas/config/tc-z80.h
+++ b/gas/config/tc-z80.h
@@ -28,7 +28,6 @@
#define TARGET_FORMAT "elf32-z80"
#endif
#define BFD_ARCH TARGET_ARCH
-#define COFF_MAGIC 0x5A80
#define TARGET_BYTES_BIG_ENDIAN 0
/* If you define this macro, GAS will warn about the
diff --git a/gas/config/tc-z8k.h b/gas/config/tc-z8k.h
index 463f1a89613..4f511e9c542 100644
--- a/gas/config/tc-z8k.h
+++ b/gas/config/tc-z8k.h
@@ -27,7 +27,6 @@ struct internal_reloc;
#define WORKING_DOT_WORD
-#define COFF_MAGIC 0x8000
#define IGNORE_NONSTANDARD_ESCAPES
#undef WARN_SIGNED_OVERFLOW_WORD
--
Alan Modra
Australia Development Lab, IBM
reply other threads:[~2023-05-30 4:22 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=ZHV5/28XpXf2d9Wd@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).