From: "Neil Schellenberger (neschell)" <neschell@cisco.com>
To: Koding <majiang31312@majiang31312>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: RE: [PATCH] MIPS support for --hash-style=gnu
Date: Thu, 14 Jan 2016 23:01:00 -0000 [thread overview]
Message-ID: <a58016f13300478989161c10bbcb09c2@XCH-RCD-006.cisco.com> (raw)
In-Reply-To: <20160105061036.1249028165@majiang31312>
[Apologies for the long delay: I have been out of the office....]
Hmm, good point.
In a separate email chain, it was also noted that DT_MIPS_SYMTABNO might be used to compute ngnusyms.
I originally avoided DT_MIPS_SYMTABNO only because I wasn't absolutely certain that it was guaranteed
that it (the number of entries in the .dynsym section) was always going to be the same as the the number of
entries in chains (plus symidx) so I decided to play it safe. That may well be needless paranoia on my part.
Opinions?
Regards,
Neil
> -----Original Message-----
> From: Koding [mailto:majiang31312@majiang31312]
> Sent: Tuesday, January 05, 2016 1:11 AM
> To: binutils@sourceware.org
> Subject: Re: [PATCH] MIPS support for --hash-style=gnu
>
> Hi all,
> I am using this patch for a loongson 3A cpu。After some tests , I
> found that there was a mistake that cause many many alignment-faults in
> this patch.
> The patch added a Elf32_Word ngnusyms in the head of .gnu.xhash
> section, then "ElfW(Addr) bitmask[maskwords]" became unaligned(8-
> bytes).
> IMO, we should change "Elf32_Word ngnusyms" to "Elf32_Xword
> ngnusyms" , or add 4-bytes pad after ngnusyms.
next prev parent reply other threads:[~2016-01-14 23:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 6:10 Koding
2016-01-14 23:01 ` Neil Schellenberger (neschell) [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-06 15:52 Jeremy Stenglein
2016-01-06 2:34 Huang Pei
2015-10-05 23:11 Neil Schellenberger (neschell)
2015-10-30 11:09 ` Nick Clifton
2015-11-05 17:14 ` Rafael Espíndola
2015-11-05 18:27 ` Neil Schellenberger (neschell)
2015-11-05 18:45 ` Rafael Espíndola
2015-11-05 23:33 ` Neil Schellenberger (neschell)
2015-11-08 13:52 ` Richard Sandiford
2015-11-09 19:05 ` Neil Schellenberger (neschell)
2016-02-05 22:38 ` Maciej W. Rozycki
2016-04-19 19:15 ` Neil Schellenberger (neschell)
2016-04-20 14:16 ` Joseph Myers
2016-04-20 16:44 ` Jim Wilson
2016-04-21 1:19 ` Maciej W. Rozycki
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=a58016f13300478989161c10bbcb09c2@XCH-RCD-006.cisco.com \
--to=neschell@cisco.com \
--cc=binutils@sourceware.org \
--cc=majiang31312@majiang31312 \
/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).