This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Target specific relocation ld integration.


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]