From: Jan Beulich <jbeulich@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] IA64: drop .bss override
Date: Fri, 5 Jan 2024 07:07:27 +0000 (GMT) [thread overview]
Message-ID: <20240105070727.8B1A9385AC1D@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=27a8c603360f55125fae98684d913aa073dc8df6
commit 27a8c603360f55125fae98684d913aa073dc8df6
Author: Jan Beulich <jbeulich@suse.com>
Date: Fri Jan 5 08:06:08 2024 +0100
IA64: drop .bss override
It doesn't look to be a good idea to override the custom handlers that
ELF and COFF have. While in this case interaction with ELF's .previous
wasn't screwed, the sub-section specifier wasn't permitted.
Diff:
---
gas/config/tc-ia64.c | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/gas/config/tc-ia64.c b/gas/config/tc-ia64.c
index 81e1d3d1a90..a1b1e61408b 100644
--- a/gas/config/tc-ia64.c
+++ b/gas/config/tc-ia64.c
@@ -68,8 +68,7 @@
enum special_section
{
/* IA-64 ABI section pseudo-ops. */
- SPECIAL_SECTION_BSS = 0,
- SPECIAL_SECTION_SBSS,
+ SPECIAL_SECTION_SBSS = 0,
SPECIAL_SECTION_SDATA,
SPECIAL_SECTION_RODATA,
SPECIAL_SECTION_COMMENT,
@@ -645,7 +644,7 @@ static const bfd_vma nop[IA64_NUM_UNITS] =
habit of setting temporary sentinels. */
static char special_section_name[][20] =
{
- {".bss"}, {".sbss"}, {".sdata"}, {".rodata"}, {".comment"},
+ {".sbss"}, {".sdata"}, {".rodata"}, {".comment"},
{".IA_64.unwind"}, {".IA_64.unwind_info"},
{".init_array"}, {".fini_array"}
};
@@ -3172,7 +3171,7 @@ dot_loc (int x)
dwarf2_directive_loc (x);
}
-/* .sbss, .bss etc. are macros that expand into ".section SECNAME". */
+/* .sbss, .srodata etc. are macros that expand into ".section SECNAME". */
static void
dot_special_section (int which)
{
@@ -5201,7 +5200,6 @@ const pseudo_typeS md_pseudo_table[] =
{ "radix", dot_radix, 0 },
{ "lcomm", s_lcomm_bytes, 1 },
{ "loc", dot_loc, 0 },
- { "bss", dot_special_section, SPECIAL_SECTION_BSS },
{ "sbss", dot_special_section, SPECIAL_SECTION_SBSS },
{ "sdata", dot_special_section, SPECIAL_SECTION_SDATA },
{ "rodata", dot_special_section, SPECIAL_SECTION_RODATA },
reply other threads:[~2024-01-05 7:07 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=20240105070727.8B1A9385AC1D@sourceware.org \
--to=jbeulich@sourceware.org \
--cc=bfd-cvs@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).