[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] constructor/destructor support
From: |
Michael Matz |
Subject: |
Re: [Tinycc-devel] constructor/destructor support |
Date: |
Wed, 27 Nov 2019 16:39:02 +0000 (UTC) |
User-agent: |
Alpine 2.21 (LSU 202 2017-01-01) |
Hi,
On Tue, 26 Nov 2019, Herman ten Brugge wrote:
> Sorry for the delay. I had a long vacation.
Nice! ;-)
> Before I went on vacation I read some Microsoft documentation.
> This documentation send me in the wrong direction.
> So the patch is now much simpler (see attachment).
I like that, push it :)
Ciao,
Michael.
>
> Regards,
>
> Herman
>
> On 2019-10-30 15:58, Michael Matz wrote:
> > Hi,
> >
> > On Wed, 30 Oct 2019, Herman ten Brugge via Tinycc-devel wrote:
> >
> >> I had a good night sleep and realized that I could copy the .init/.fini
> >> arrays relocations to the text section
> > Why to the text section (and not, say .data, .init_array contains
> > pointers, not code), and why copying at all? The link process (i.e.
> > pe_assign_addresses) merely needs to make sure that .init/.fini becomes
> > part of the loaded image (which should already be the case without any
> > changes?), then the start/stop symbols (why aren't you using
> > add_init_array_defines?) point to the correct areas in that image and
> > should be accessible just fine from the crt startup code.
> >
> >
> > Ciao,
> > Michael.
>
>