Re: For example only, updated Windows DLL support and gdbserver DLL support

["Ulrich Weigand" <uweigand@de.ibm.com>]

Dan Jacobowitz wrote:

> > It looks like the only way to get this to work within the regular solib
> > framework would be to actually teach solib.c itself about this form of
> > archive members.
> 
> Yes, I think you're right.  How about we add an optional member=""
> attribute to <library>, and make the common solib.c code open it?
> We'd also have to allow .o files.

That sounds reasonable.  The member name would presumably also
have to be added to so_list ...

> I'm not sure how much trouble you'll have reporting the correct
> relocations for an object file.  Do you get something based on
> sections, or do AIX object files have a fixed number of segments?

XCOFF seems to be a bit limited in that respect, I understand there
is just "Text" and "Data".  The AIX ldinfo structure provides:

ldinfo_textorg
    Effective address of the loaded program image, including the XCOFF headers. 

ldinfo_textsize
    Length of loaded program image. 

ldinfo_dataorg
    Effective address of the start of data. 

ldinfo_datasize
    Size of data, including the .bss section. 

For more details, see:
http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.files/doc/aixfiles/ldr.h.htm


Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com