On Tue, Aug 29, 2006 at 01:14:12AM +0200, Eugeniy Meshcheryakov wrote: > Hello, > > 27 ?????? 2006 ? 17:12 +0200 Eugeniy Meshcheryakov ???????(-??): > > > Anyway, arm needs an arm_retval.c and arm_regs.c in backends/ > > Ok, I'll work on arm then. > > Patch for arm support is attached. It however adds support for only one > ABI variant supported by gcc (default one, -mabi=apcs-gnu -mhard-float).
I've been looking at the ABI doc, and it's nice to see someone actually documented this. This is like only the second arch for what I find it. The ABI doc seems to say that 16-23 can be used for both f0-f7 and s0-f7, and s0-s31 can also be in 64-95. I guess there is no way to see which ABI is being used? The gdb source seems to have r0-r12, sp, lr, pc, instead of r0-r15. The ABI document also seem to be suggesting those. It seems those can be used intermixed. The binutils source also seems to have an sl and fp, for use with gcc at r11 and r12. gdb also seems to have fps and cpsr after f0-f7, where fps doesn't seem to be documented, while the ABI doc seems to say that CPSR isn't assigned a number. So, this looks good at first sight. > Support for -msoft-float can be added easily if if will be possible to > get e_flags member from ELF header in arm_return_value_location(), but I > do not see how it can be done. > > I also do not see how it is possible to add support for other ABIs now, > AFAIKS gcc/binutils do not put information about ABI to ELF file. I don't know, but you should try running elfutils -h on a binary or something, maybe it can tell. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
