On Saturday 02 January 2010 16:42:23, Danny Backx wrote: > On Fri, 2010-01-01 at 16:24 +0000, Pedro Alves wrote: > > FYI, I hadn't applied the ld patch myself because I was > > looking to confirm/hear if there's another cleaner way > > to get at the image base, but I can't find one. Anyway, I've > > now commited the mingw/pseudo-reloc patch. (A bit cleaned up from > > yesterday's, reducing divergence from upstream mingw). > > Looks like I committed only part, apologies.
Sounds like the message came across with phase inverted. > I did some more testing and saw strange things that I need to look into > further. libexpat still works on the emulator but not on my real device. > It did so before. Boo. > Question : how certain are we that pseudo-relocation v2 is a requirement > for all this ? I've seen improvements when doing the section move > operations (no more separate .bss, .idata, .edata) but I've never > actually seen a difference between v1 and v2, I took comments about that > for granted. It can only possibly make a difference if pseudo-relocs are actually used. Are you clear on what pseudo-relocs are? I haven't actually tested anything that generates a pseudo-reloc (v1 or v2) on WM6.1 yet. That being said, I don't know what Kai's patch actually does --- it is perhaps related to stopping ld from making sections with pseudo-relocs (.text, .rdata) writable? That may be required. I tried to look at the binutils patches that you've applied to svn, but they're all kind of mixed up. Would it be possible to split them up? I guess that's what you're trying to do? I can't distinguish what's Kai's changes from your WM6.1 related changes. I thought of starting with only the base relocation (__text_start__) patch against a pristine upstream binutils, and work up what is really needed for WM6.1 --- we may find out that not much else is required, but gave up when I couldn't quickly distinguish what is what. -- Pedro Alves ------------------------------------------------------------------------------ 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
