This is the mail archive of the crossgcc@cygnus.com mailing list for the crossgcc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
The Idea is to not use the compiler. The compiler creates the 3 usual sections, text, data bss The linker creates arbitrary "OUTPUT" sections by taking the desired parts (text,data, bss) of an individual file and putting in the arbitrarity named "output" section. The limitation (I believe) is that all the text or data or bss from an individual object file must go into 1 "output" section. We use this to put different parts of .text into flash or ram. It is rather ugly to hard code sourcefile.o in linker scripts but it works reliably. -----Original Message----- From: Josef Wolf [SMTP:jw@raven.inka.de] Sent: Wednesday, April 01, 1998 5:17 PM To: Stephen Williams Cc: jw@raven.inka.de; crossgcc@cygnus.com Subject: Re: crossgcc: arbitrary sections? Hello! > You can most certainly do what you want with coff. My favorite method is > to use linker scripts. Seems that it depends how the toolchain is compiled. On my installation (--target=m68k-coff, one-tree-build) gcc complains while _compiling_, not while linking. So linker scripts don't have any chance to change the behavior at this early stage.