public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
* Target specific relocation ld integration.
@ 2014-07-03 13:07 Dominique Torette
  2014-07-04  9:57 ` Nicholas Clifton
  0 siblings, 1 reply; 2+ messages in thread
From: Dominique Torette @ 2014-07-03 13:07 UTC (permalink / raw)
  To: binutils

Hi,

I'm porting the GNU binutils to an' in-house' microcontroller.
I've followed the http://www.opensourceforu.com/2010/01/binutils-porting-guide-to-a-new-target-architecture/
It seems that the libbfd is quite complete. I can use most of binutils, except the . linker.
It works except the relocations. My input format is elf32.
I have only one simple relocation schema for 'jump' like instructions.
The format for these instructions are the opcode on 32 bits, followed by the absolute 32 bits address of the jump.
I have defined an 'elf32-myArch.c' file to define the reloc_map, reloc_howt_type, the reloc_type_lookup and the reloc_name_lookup.
I've tried to run the ld command under debugger and set breakpoint on my reloc_type_lookup and reloc_name_lookup functions.
But I never reach these breakpoints! I've tried a step-by-step execution, but I didn't seen where and how the target specific relocation functions are registered.
Could you give some additional hints to integrate my target specific relocation schema.

Thanks in advance, Dominique Torette.

Dominique Torette
System Architect
Rue des Chasseurs Ardennais - Liège Science Park - B-4031 Angleur
Tel: +32 (0) 4 361 81 11 - Fax: +32 (0) 4 361 81 20
www.spacebel.be



 ------------------------------------------------------------------------------

E-MAIL DISCLAIMER

The present message may contain confidential and/or legally privileged information. If you are not the intended addressee and in case of a transmission error, please notify the sender immediately and destroy this E-mail. Disclosure, reproduction or distribution of this document and its possible attachments is strictly forbidden.

SPACEBEL denies all liability for incomplete, improper, inaccurate, intercepted, (partly) destroyed, lost and/or belated transmission of the current information given that unencrypted electronic transmission cannot currently be guaranteed to be secure or error free.
Upon request or in conformity with formal, contractual agreements, an originally signed hard copy will be sent to you to confirm the information contained in this E-mail.

SPACEBEL denies all liability where E-mail is used for private use.

SPACEBEL cannot be held responsible for possible viruses that might corrupt this message and/or your computer system.
 -------------------------------------------------------------------------------

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

* Re: Target specific relocation ld integration.
  2014-07-03 13:07 Target specific relocation ld integration Dominique Torette
@ 2014-07-04  9:57 ` Nicholas Clifton
  0 siblings, 0 replies; 2+ messages in thread
From: Nicholas Clifton @ 2014-07-04  9:57 UTC (permalink / raw)
  To: Dominique Torette, binutils

Hi Dominique,

> The present message may contain confidential and/or legally
> privileged information. If you are not the intended addressee
> and in case of a transmission error, please notify the sender
> immediately and destroy this E-mail. Disclosure, reproduction
> or distribution of this document and its possible attachments
> is strictly forbidden.

I would love to answer your question, but this disclaimer prevents that. 
  Perhaps you could post your question from a different account ?

Cheers
   Nick


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

end of thread, other threads:[~2014-07-04  9:57 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-07-03 13:07 Target specific relocation ld integration Dominique Torette
2014-07-04  9:57 ` Nicholas Clifton

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