Mitko <asdfgga12@xxxxxxxxx> writes: > I am writing you directly because the issue is associated with IAR ARM > tools, so the might have some concerns regarding the release of > information. > > I was trying recently Sourcery G++ Lite 2010q1-188 for ARM EABI (GNU > assembler verson 2.19.51). > > In general it was comiling some basic files, but wen tried to link the > produced obj file with IAR linker got an error that the entry point of > the program can't be found. > > I did contacted IAR and they responded that EWARM tools are use ARM > ABI ELF/Dwarf standard version 2.06B. > > Wondered on what version of ELF/DWART standard current gcc version > supports as well as if you can recommend a way for converting elf > files in different version formats? Well, you wrote to the mailing list rather than writing to me directly, but that's just as well because I don't know the answer. Sorry. I know that gcc supports the ARM EABI, but I don't know the version number and I don't know if that is the same as the ARM ABI 2.06B, whatever that is. In my experience most people call the ARM EABI the EABI, not the ABI. There are other, older and hopefully obsolete ARM ABIs, that most people call names like APCS, ATPCS, AAPCS, etc. So I don't know what the ARM ABI is. Most linkers have an option, usually the -e option, which you can use to set the entry point of the program. Whether you can convert from one ELF version to another by a post-compilation tool depends entirely on the differences between the two ELF versions, which in this case I don't know. It is normally impossible, as normally the differences are at the level of calling conventions which can only be handled at compilation time. However, it may be possible in the specific case you are concerned about. Or, if the only problem is the entry point, you can probably handle that via a command line option. Ian
