From: jont AT harlequin DOT co DOT uk (Jon Thackray) Subject: Re: Section attributes from ld 16 Jul 1997 11:53:06 -0700 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: <199707161043.LAA27094.cygnus.gnu-win32@zaphod.long.harlequin.co.uk> References: <199707151105 DOT MAA14711 AT zaphod DOT long DOT harlequin DOT co DOT uk> <199707152216 DOT SAA07402 AT tweedledumb DOT cygnus DOT com> Original-To: ian AT cygnus DOT com Original-Cc: gnu-win32 AT cygnus DOT com In-Reply-To: <199707152216.SAA07402@tweedledumb.cygnus.com> Original-Sender: owner-gnu-win32 AT cygnus DOT com ian AT cygnus DOT com writes: > >How does ld determine which attributes sections are to have? By > >attributes, I mean things like:- > > >Contains code, contains initialised data, should be loaded with > >execute permission, should be loaded with read permission, should be > >loaded with write permission etc. > > The attributes are based on the attributes of the input sections which > are mapped into the output sections. Take a look at > gas/config/obj-coff.c to see how to use the .section directive in an > assembler file. I will look at this. However... My input sections (in the case where I'm having problems) all have attribute MEM_READ, whereas the resulting link section doesn't. It would appear that link is overriding this in some way. - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".