This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Tue, 11 Nov 2003, Dmitry Semyonov wrote: > I'm trying to create an object file from a C source with the following > function: [...] > (arm-wince-pe-gcc -fno-leading-underscore -S str_test.c) produces > the following asm output: [...] > Microsoft linker from WinCE 4.2 expects both L2 and L2+4 words to be > zeros in object file. (Actual addresses of LC0 and LC1 strings are > _added_ to L2 and L2+4 words during linking). But L2+4 word contains > value of 8 (offset of LC1 string) instead. > > Is there an option to control the behavior of gas in the way MS linker > expects? > > If not then it is a bug in gas or bfd. I'm currently trying to determine > the exact place. Any help would be welcome, since I'm not very familiar > with binutils. Well, the bug was found. Thanks Victor Vengerov from Oktet for helping with determining the right place for a fix. It is in bfd/coff-arm.c: partial_inplace field(s?) of static aoutarm_std_reloc_howto structure is(are?) defined so that resulting object files are incompatible with MS linker. I want to peform more testing to be sure our changes are not breaking some functionality. Then I'll submit a patch. ...Bye..Dmitry. ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |