From: Daniel Jacobowitz <drow@false.org>
To: Frederic RISS <frederic.riss@st.com>
Cc: Jim Blandy <jimb@codesourcery.com>,
Steven Johnson <sjohnson@sakuraindustries.com>,
gdb@sources.redhat.com
Subject: Re: Problems with startup code symbols (Copious warnings)
Date: Tue, 20 Jun 2006 12:56:00 -0000 [thread overview]
Message-ID: <20060620123712.GA20631@nevyn.them.org> (raw)
In-Reply-To: <1150806737.2480.71.camel@crx549.cro.st.com>
On Tue, Jun 20, 2006 at 02:32:17PM +0200, Frederic RISS wrote:
> Of course. But I don't see any non-embedded binary with a section loaded
> at NULL.
Probably...
> And I don't see much embedded bootcode needing linkonce
> sections.
... but not probably.
Typical for a lot of embedded devices I've worked with is to have a
single massive ELF image, including boot code and the entire remainder
of the image, and to use C++ for most of it. I've definitely worked
with images where this wouldn't help.
> > Is that an improvement? I guess so.
>
> It's certainly better than the current HAS_RELOCS check.
Yes, I think so. Want to do it, anybody?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-20 12:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 7:23 Steven Johnson
2006-06-08 9:06 ` Jim Blandy
2006-06-08 12:25 ` Steven Johnson
2006-06-08 23:10 ` Steven Johnson
2006-06-15 0:12 ` Jim Blandy
2006-06-15 7:33 ` Jim Blandy
2006-06-19 9:36 ` Frederic RISS
2006-06-20 12:23 ` Daniel Jacobowitz
2006-06-20 12:33 ` Frederic RISS
2006-06-20 12:56 ` Daniel Jacobowitz [this message]
2006-06-20 13:09 ` Frederic RISS
2006-06-20 20:17 ` Steven Johnson
2006-06-20 23:35 ` Daniel Jacobowitz
2006-06-21 8:54 ` Frederic RISS
2006-06-21 14:44 ` Steven Johnson
2006-06-21 15:28 ` Daniel Jacobowitz
2006-06-19 10:00 ` Steven Johnson
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=20060620123712.GA20631@nevyn.them.org \
--to=drow@false.org \
--cc=frederic.riss@st.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@codesourcery.com \
--cc=sjohnson@sakuraindustries.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