Date:	Mon, 29 Jul 1996 14:31:25 +0200 (MET DST)
From:	Mark Habersack <grendel AT ananke DOT amu DOT edu DOT pl>
To:	Ray Kelm <rhk AT farpoint DOT newimage DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: __attribute__((section))
In-Reply-To:	<Dv8JpK.rn@farpoint.newimage.com>
Message-ID:	<Pine.NEB.3.93.960729142816.2833D-100000@ananke.amu.edu.pl>
MIME-Version:	1.0

On Sun, 28 Jul 1996, Ray Kelm wrote:

>Mark Habersack (grendel AT ananke DOT amu DOT edu DOT pl) wrote:
>
>: Messing up with sections of COFF images produced by djgpp I tried to put some
>: data into the separate section using the (section) attribute. Unfortunately
>: gcc aborts saying that "current target doesn't support sections" (not the
>: exact message but the meaning is the same). So how it is? Object files output
>: by gcc are COFF, right? They support many sections and put no restriction on
>

>I traced this problem for a ways into the code, and it seemed that the
>problem was actually in binutils (libbfd). Beyond that I didn't have enough
>time to really dig into it.
I think it's not a problem of libbfd. I have used the BFD lib to create
multi-sectioned COFF images (BTW. .o files and non-stubbed, linked execs are
share exactly the same format - i.e. every .o WOULD have been stubbed!). GAS,
ld also use BFD and ARE ABLE to create multi-sectioned COFFs. The problem
seems to live in cc*.exe themselves.

See you, Mark

/*******************************/
/** So here I am once more... **************************************/
/** When you grown up and leave your playground, where you kissed **/
/** your Prince and found your Frog - remember the Jester that    **/
/** showed you tears, a Script for Tears... ************************/
/*********************************************/

- Raw text -