From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] display the entry point when compiling a stand-alone program
Date: Fri, 11 Jun 2010 16:46:45 +0200 [thread overview]
Message-ID: <m2fx0tsk2y.fsf@ohwell.denx.de> (raw)
In-Reply-To: <1276203289-19488-1-git-send-email-timur@freescale.com> (Timur Tabi's message of "Thu, 10 Jun 2010 15:54:49 -0500")
Hi Timur,
> Contrary to popular belief, the entry point for a stand-alone program is not
> consistent. The only way to know for sure is to use the nm program and
> search for the entry point function. So we update the Makefile build rule
> to display this entry point after the ELF image is created.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>
I was thinking along the same lines but decided that this is not the
correct solution but only sweetening the fall ;)
We should concentrate on creating a correct linker script so that the
entry point ends up where we want it to be, namely at
STANDALONE_LOAD_ADDR.
Can you have a look at this and maybe solve the problem for good then?
Thanks!
Detlev
--
Der erfahrene Politiker hantiert mit Werten wie mit Fahnen. Man tut so,
als ob klar sei, was gerecht ist, und unterstellt jedem, der dar?ber
diskutieren will, er sei dagegen. -- Norbert Bolz
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de
next prev parent reply other threads:[~2010-06-11 14:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 20:54 [U-Boot] [PATCH] display the entry point when compiling a stand-alone program Timur Tabi
2010-06-11 14:46 ` Detlev Zundel [this message]
2010-06-11 15:28 ` Timur Tabi
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=m2fx0tsk2y.fsf@ohwell.denx.de \
--to=dzu@denx.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.