On Wed, 30 Dec 2009 15:16:11 +0000, Pedro Alves <alves....@gmail.com> wrote: > On Wednesday 30 December 2009 14:56:18, Vincent R. wrote: >> >> > #if defined(TARGET_IS_arm_wince_pe) >> > /* Windows CE ignores the image base, but we want to >> > be compatible with MSFT's tools. */ >> > #undef NT_DLL_IMAGE_BASE >> > #define NT_DLL_IMAGE_BASE 0x00010000 >> > #endif >> >> OK but I still don't understand this comment. Pedro what do you mean by >> compatible with >> MSFT's tools ? > > "compatible" here just meant, do the same as MSFT's linker does. > 0x10000 was the image base Visual Studio was setting by default > at the time I wrote that. This minimized spurious differences > when comparing dumps of images generated with ld with MSFT > generated images. Since this change is in our binutils copy since > 2006, I'm confused when you say only recent binutils started > using 0x10000 as image base. I don't think this hunk is > in upstream binutils --- could it be that you were using > a pristine binutils from upstream before?
Yes you are right I think I was using some custom binutils but now I understand what you meant I suppose its better to declare it as 0x10000000 because this is what MS linker uses now. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Cegcc-devel mailing list Cegcc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cegcc-devel
