From: Jan Beulich <jbeulich@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] gas: drop unused fields from struct segment_info_struct
Date: Fri, 1 Dec 2023 07:30:16 +0000 (GMT) [thread overview]
Message-ID: <20231201073016.D719B3857B81@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2d9b910d5612d802b3c68f04ec69b08e356c503e
commit 2d9b910d5612d802b3c68f04ec69b08e356c503e
Author: Jan Beulich <jbeulich@suse.com>
Date: Fri Dec 1 08:29:33 2023 +0100
gas: drop unused fields from struct segment_info_struct
user_stuff, dot, and lineno_list_{head,tail} have no users (left), while
bfd_section was only ever written.
Diff:
---
gas/subsegs.c | 1 -
gas/subsegs.h | 12 +-----------
2 files changed, 1 insertion(+), 12 deletions(-)
diff --git a/gas/subsegs.c b/gas/subsegs.c
index ae42b4e76d9..a74db52637a 100644
--- a/gas/subsegs.c
+++ b/gas/subsegs.c
@@ -61,7 +61,6 @@ alloc_seginfo (segT seg)
seginfo = obstack_alloc (¬es, sizeof (*seginfo));
memset (seginfo, 0, sizeof (*seginfo));
- seginfo->bfd_section = seg;
bfd_set_section_userdata (seg, seginfo);
}
/*
diff --git a/gas/subsegs.h b/gas/subsegs.h
index ace0657bdfb..2bc7adacc56 100644
--- a/gas/subsegs.h
+++ b/gas/subsegs.h
@@ -71,23 +71,13 @@ typedef struct segment_info_struct {
there are frags. */
unsigned int bss : 1;
- int user_stuff;
-
/* Fixups for this segment. This is only valid after the frchains
are run together. */
fixS *fix_root;
fixS *fix_tail;
- symbolS *dot;
-
- struct lineno_list *lineno_list_head;
- struct lineno_list *lineno_list_tail;
-
- /* Which BFD section does this gas segment correspond to? */
- asection *bfd_section;
-
/* NULL, or pointer to the gas symbol that is the section symbol for
- this section. sym->bsym and bfd_section->symbol should be the same. */
+ this section. */
symbolS *sym;
/* Used by dwarf2dbg.c for this section's line table entries. */
reply other threads:[~2023-12-01 7:30 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=20231201073016.D719B3857B81@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).