From: Shinya Kuribayashi <skuribay@ruby.dti.ne.jp>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Fixed the _gp/_G_O_T_ confusion for good
Date: Sun, 21 Oct 2007 10:22:44 +0900 [thread overview]
Message-ID: <471AA9E4.4030504@ruby.dti.ne.jp> (raw)
In-Reply-To: <470F6339.6070102@comsys.ro>
Sorry for late.
Vlad Lungu wrote:
> $gp is loaded with _gp
> the GOT is updated starting from _G_O_T_+8 up to (but not including)
> __got_end
> __got_start is unused num_got_entries is unused and could be removed
> from ld scripts
I'll take this fix except for removing __got_start and num_got_entries.
I know you want to make it work whether __got_start is out of alignment
or not, but that is a little mess. We should fix num_got_entries part
instead, and update GOT entries using _GLOBAL_OFFSET_TABLE_ and
num_got_entries. This is easily understandable and straight forward :-)
I've submitted patches. Plase review.
thanks,
Shinya
prev parent reply other threads:[~2007-10-21 1:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 12:06 [U-Boot-Users] [PATCH] Fixed the _gp/_G_O_T_ confusion for good Vlad Lungu
2007-10-21 1:22 ` Shinya Kuribayashi [this message]
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=471AA9E4.4030504@ruby.dti.ne.jp \
--to=skuribay@ruby.dti.ne.jp \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox