From: Alan Modra <amodra@bigpond.net.au>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "H. J. Lu" <hjl@lucon.org>, Paul Brook <paul@codesourcery.com>,
binutils@sourceware.org, Paul Koning <pkoning@equallogic.com>,
vgoyal@redhat.com, drow@false.org, binutils@sources.redhat.com
Subject: Re: Linker Bug or Design Intent (Absolute symbols in zero sized sections)
Date: Fri, 13 Oct 2006 11:26:00 -0000 [thread overview]
Message-ID: <20061013013852.GB20843@bubble.grove.modra.org> (raw)
Message-ID: <20061013112600.N1E0gjsZZorneQUdbH2MeGaTr50UvHnKXEgr4-5ZLtE@z> (raw)
In-Reply-To: <20061012143409.GI20982@devserv.devel.redhat.com>
On Thu, Oct 12, 2006 at 10:34:09AM -0400, Jakub Jelinek wrote:
> On Thu, Oct 12, 2006 at 01:13:41PM +0930, Alan Modra wrote:
> > > Against emitting empty sections speaks both that it is a wasted space
> > > in section header table/.shstrtab, but more importantly that empty
> > > sections are an endless source of bugs
> >
> > Agreed.
> >
> > If we are to remove them, then
> > a) Detecting a symbol assignment in a linker script should result in the
> > section alignment and vma being honoured.
>
> Not sure what are we doing ATM here.
The wrong thing..
> > b) All the ELF backends will need changes so that removed output section
> > syms are never used when emitting relocs. At the same time, we may
> > as well just use one section sym for all relocs (or two for targets
> > that might want to relocate the data segment separately from the text
> > segment).
>
> Sure.
>
> > c) _bfd_fix_excluded_sec_syms should be changed to not create absolute
> > syms.
>
> And instead have the nearest section in the same loadable segment in
> st_shndx?
Something like that. I figured on just using the closest preceding
section. BTW, I started throwing a patch together to do (b).
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2006-10-13 1:38 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 14:33 Vivek Goyal
2006-09-26 14:49 ` H. J. Lu
2006-09-26 14:52 ` Vivek Goyal
2006-09-26 15:13 ` H. J. Lu
2006-09-26 15:41 ` Daniel Jacobowitz
2006-09-26 15:54 ` Vivek Goyal
2006-09-26 16:21 ` H. J. Lu
2006-09-26 16:30 ` Vivek Goyal
2006-09-26 16:44 ` H. J. Lu
2006-09-26 16:45 ` Vivek Goyal
2006-09-26 17:01 ` Daniel Jacobowitz
2006-09-26 23:50 ` Alan Modra
2006-09-27 1:51 ` Daniel Jacobowitz
2006-09-27 3:09 ` Daniel Jacobowitz
2006-09-26 17:48 ` Paul Koning
2006-09-26 23:53 ` Alan Modra
2006-09-28 17:01 ` Paul Brook
2006-09-28 17:05 ` Paul Brook
2006-09-28 18:37 ` H. J. Lu
2006-09-28 18:53 ` H. J. Lu
2006-10-10 16:41 ` Jakub Jelinek
2006-10-10 16:51 ` Jakub Jelinek
2006-10-11 3:52 ` Jakub Jelinek
2006-10-11 7:12 ` Jakub Jelinek
2006-10-11 8:04 ` Alan Modra
2006-10-11 14:08 ` Alan Modra
2006-10-11 14:19 ` Jakub Jelinek
2006-10-11 14:45 ` Jakub Jelinek
2006-10-12 10:18 ` Alan Modra
2006-10-12 14:37 ` Alan Modra
2006-10-13 10:58 ` Jakub Jelinek
2006-10-13 11:10 ` Alan Modra [this message]
2006-10-13 11:26 ` Alan Modra
2006-10-17 16:02 ` Dynamic section symbols, ignored output sections Alan Modra
2006-10-19 14:55 ` ligang
2006-10-22 0:25 ` Jakub Jelinek
2006-10-23 14:13 ` Alan Modra
2006-09-29 6:42 ` Linker Bug or Design Intent (Absolute symbols in zero sized sections) Alan Modra
2006-09-29 8:06 ` Alan Modra
2006-09-26 16:14 ` H. J. Lu
2006-09-26 16:40 ` Vivek Goyal
2006-09-26 17:57 ` Vivek Goyal
2006-09-26 20:23 ` H. J. Lu
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=20061013013852.GB20843@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=hjl@lucon.org \
--cc=jakub@redhat.com \
--cc=paul@codesourcery.com \
--cc=pkoning@equallogic.com \
--cc=vgoyal@redhat.com \
/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).