Re: [fpc-devel] Some questions about compiler work on x86_64-win64

Am 17.03.2017 22:16 schrieb "Bishop" : > > 03/17/17 11:56:47, Sven Barth via fpc-devel < fpc-devel@lists.freepascal.org>: > > >> 1) EXE-file contained .CRT section. As i understand it contained one pointer to _FPC_Tls_Callback functions from RTL. Is it used only for this? > > Correct. > And main se

Re: [fpc-devel] Some questions about compiler work on x86_64-win64

03/17/17 11:56:47, Sven Barth via fpc-devel : >> 1) EXE-file contained .CRT section. As i understand it contained one pointer to _FPC_Tls_Callback functions from RTL. Is it used only for this? > Correct. And main sence of this function is allocated ThreadVar

Re: [fpc-devel] Some questions about compiler work on x86_64-win64

On 17/03/17 10:56, Sven Barth via fpc-devel wrote: I might remember it incorrectly, but I think that Microsoft says that all accesses should be RIP relative to reduce the need for relocations. Probably also for ASLR. Jonas ___ fpc-devel maillist -

Re: [fpc-devel] Some questions about compiler work on x86_64-win64

Am 17.03.2017 08:08 schrieb "Bishop via fpc-devel" < fpc-devel@lists.freepascal.org>: > > I have some questions about compiler work on x86_64-win64. > > 1) EXE-file contained .CRT section. As i understand it contained one pointer to _FPC_Tls_Callback functions from RTL. Is it used only for this? C

[fpc-devel] Some questions about compiler work on x86_64-win64

I have some questions about compiler work on x86_64-win64. 1) EXE-file contained .CRT section. As i understand it contained one pointer to _FPC_Tls_Callback functions from RTL. Is it used only for this? 2) Why INITFINAL table on both Windows and Linux puted to .data section? Is we need to c