public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
* RFE: relocation type for clustered *_RELATIVE relocations
@ 2012-07-12 13:38 John Reiser
  2012-07-12 13:55 ` Joseph S. Myers
  0 siblings, 1 reply; 2+ messages in thread
From: John Reiser @ 2012-07-12 13:38 UTC (permalink / raw)
  To: Binutils

I've just seen a shared library with more than 30,000 R_ARM_RELATIVE
relocations, and where the .r_offset span only 0x42a00 bytes.
This is an average of 8.9 bytes from one .r_offset to the next.

It would be handy if there were an R_ARM_VEC_RELATIVE relocation type
where ELF32_R_SYM(.r_info) gave a count of consecutive addresses,
or an R_ARM_MAP_RELATIVE where ELF32_R_SYM(.r_info) was a bitmap
for for applying RELATIVE relocation to the 24 addresses which
follow .r_offset (thus up to 25 relocations per Elf32_Rel.)
Of course, another choice would be to extend the meaning
of the existing R_ARM_RELATIVE with one of these two cases.

Comments?

-- 

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: RFE: relocation type for clustered *_RELATIVE relocations
  2012-07-12 13:38 RFE: relocation type for clustered *_RELATIVE relocations John Reiser
@ 2012-07-12 13:55 ` Joseph S. Myers
  0 siblings, 0 replies; 2+ messages in thread
From: Joseph S. Myers @ 2012-07-12 13:55 UTC (permalink / raw)
  To: John Reiser; +Cc: Binutils

On Thu, 12 Jul 2012, John Reiser wrote:

> It would be handy if there were an R_ARM_VEC_RELATIVE relocation type

As far as I know, arm.eabi@arm.com is the address for requesting changes 
or additions to the ARM EABI specifications.

-- 
Joseph S. Myers
joseph@codesourcery.com

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-07-12 13:55 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-07-12 13:38 RFE: relocation type for clustered *_RELATIVE relocations John Reiser
2012-07-12 13:55 ` Joseph S. Myers

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).