From: Hiroki Kaminaga <kaminaga@sm.sony.co.jp>
To: binutils@sourceware.org
Cc: kaminaga@sm.sony.co.jp
Subject: use of gnu hash for MIPS
Date: Wed, 28 Feb 2007 07:09:00 -0000 [thread overview]
Message-ID: <20070228.152304.92590588.kaminaga@sm.sony.co.jp> (raw)
Hi,
Currently, MIPS support for gnu hash is disabled:
http://sourceware.org/ml/binutils/2006-07/msg00341.html
but I eager to use it!
To overcome the problem of .dynsym sorting order conflict mentioned
above, is there good idea?
What I could come was following:
1) make .gnu.dynsym section
- which is specific for .gnu.hash, but obiously redundant
2) allow bitmap portion of gnu hash for MIPS
- to benefit speedup of that part (which is not bad idea, I think)
- the symbol lookup part is same as before
3) Somehow work out to co-existance of sorting order of .dynsym
Regarding choice 3), my understanding is as follows:
.got requires order of
+------------+
| local sym |
| local sym |
+------------+ <- DT_MIPS_LOCAL_GOTNO
| extern sym |
| extern sym |
| extern sym |
+------------+
but there is no constraints in ordering. (except to be 1:1 with
.dynsym) On the other hand, gnu hash sorts .dynsym in hash value
order. So, does this method work?
1) locate local symbols on first part
- to obey .got requirement
2) locate external sorted by hash after local symbols
- to apply gnu hash
3) sort .got entries according to hash value
- to obey .got 1:1 with .dynsym
Any advice?!
Best Regards,
# Please Cc: me, I'm not subscribed.
(Hiroki Kaminaga)
t
--
next reply other threads:[~2007-02-28 6:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 7:09 Hiroki Kaminaga [this message]
2007-03-13 16:04 ` Richard Sandiford
2007-08-27 15:03 ` [RFC][PATCH][EXPERIMENTAL] enable MIPS gnu hash (was: Re: use of gnu hash for MIPS) Hiroki Kaminaga
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=20070228.152304.92590588.kaminaga@sm.sony.co.jp \
--to=kaminaga@sm.sony.co.jp \
--cc=binutils@sourceware.org \
/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).