|
@@ -926,7 +926,7 @@ implementation
|
|
,oso_keep
|
|
,oso_keep
|
|
{$endif FPC_USE_TLS_DIRECTORY}
|
|
{$endif FPC_USE_TLS_DIRECTORY}
|
|
],
|
|
],
|
|
- {pdata} [oso_load,oso_readonly,oso_keep],
|
|
|
|
|
|
+ {pdata} [oso_data,oso_load,oso_readonly {$ifndef x86_64},oso_keep{$endif}],
|
|
{stub} [oso_Data,oso_load,oso_readonly,oso_executable],
|
|
{stub} [oso_Data,oso_load,oso_readonly,oso_executable],
|
|
{data_nonlazy} [oso_Data,oso_load,oso_write],
|
|
{data_nonlazy} [oso_Data,oso_load,oso_write],
|
|
{data_lazy} [oso_Data,oso_load,oso_write],
|
|
{data_lazy} [oso_Data,oso_load,oso_write],
|
|
@@ -1001,8 +1001,10 @@ implementation
|
|
{ For idata (at least idata2) it must be 4 bytes, because
|
|
{ For idata (at least idata2) it must be 4 bytes, because
|
|
an entry is always (also in win64) 20 bytes and aligning
|
|
an entry is always (also in win64) 20 bytes and aligning
|
|
on 8 bytes will insert 4 bytes between the entries resulting
|
|
on 8 bytes will insert 4 bytes between the entries resulting
|
|
- in a corrupt idata section }
|
|
|
|
- sec_idata2,sec_idata4,sec_idata5,sec_idata6,sec_idata7:
|
|
|
|
|
|
+ in a corrupt idata section.
|
|
|
|
+ Same story with .pdata, it has 4-byte elements which should
|
|
|
|
+ be packed without gaps. }
|
|
|
|
+ sec_idata2,sec_idata4,sec_idata5,sec_idata6,sec_idata7,sec_pdata:
|
|
result:=4;
|
|
result:=4;
|
|
else
|
|
else
|
|
result:=sizeof(pint);
|
|
result:=sizeof(pint);
|