From: "H. J. Lu" <hjl@lucon.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Daniel Jacobowitz <drow@false.org>, binutils@sources.redhat.com
Subject: Re: Linker Bug or Design Intent (Absolute symbols in zero sized sections)
Date: Tue, 26 Sep 2006 16:21:00 -0000 [thread overview]
Message-ID: <20060926161028.GB9105@lucon.org> (raw)
In-Reply-To: <451941EB.3000207@redhat.com>
On Tue, Sep 26, 2006 at 11:06:19AM -0400, Vivek Goyal wrote:
> Daniel Jacobowitz wrote:
> >On Tue, Sep 26, 2006 at 07:51:59AM -0700, H. J. Lu wrote:
> >
> >>I think for --emit-relocs, we can keep an empty output section if its
> >>address is taken.
> >>
> >>Of course, we need to update linker doc.
> >
> >
> >I think we're being too specific to this case.
> >
> >Why are we changing what the linker script clearly defines as section
> >relative symbols to absolute symbols? This isn't the only use case
> >I've encountered where that will break. We should either discard the
> >symbols, or leave the empty section.
> >
>
> I think retaining the zero sized section might be more logical otherwise
> a user who has specifically defined a section relative symbol in linker
> script file will be surprised to know that in some cases symbol is not
> present at all.
I think removing empty output sections isn't a bad idea. Otherwise,
a normal executable/DSO may have many empty output sections since
the default linker scripts may have many unused output sections.
However, I agree that removing empty output sections shouldn't lead
to many surprises for user. I think linker
1. Should remove an empty output section if it isn't used to define
section relative symbol which may be changed at run time.
2. Shouldn't convert a section relative symbol to absolute symbol
if it may be changed at run time.
3. Should preserve the pre-set constant VMA of an empty output section.
Is there anything I missed?
H.J.
next prev parent reply other threads:[~2006-09-26 16:10 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 [this message]
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
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=20060926161028.GB9105@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.com \
--cc=drow@false.org \
--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).