On 10.03.2019 13:48, Jonas Maebe wrote:
On 10/03/2019 11:40, Yuriy Sydorov wrote:
If I recall correctly, currently the compiler uses longints as stack offsets internally in several places. That's why
the limit is 2GB even for 64-bit targets.
That would be compiler bugs that need to be fixed. I
Hi,
On Sun, 10 Mar 2019, Jonas Maebe wrote:
> It's always possible to add a hint about efficiency in case the size of
> the locals grows beyond offsets that can be embedded in a single
> instruction, although this hint would trigger already at 32KB of locals
> on e.g. PowerPC.
I'm all for such a
On 10/03/2019 11:40, Yuriy Sydorov wrote:
If I recall correctly, currently the compiler uses longints as stack
offsets internally in several places. That's why the limit is 2GB even
for 64-bit targets.
That would be compiler bugs that need to be fixed. Ideally, the commit
message would also h
On 10.03.2019 12:07, Jonas Maebe wrote:
On 2019-03-10 10:22, Yuriy Sydorov wrote:
FYI on 64-bit Windows the stack size limit is hard coded to 1GB. The
same 1GB limit applies on 32-bit Windows. Probably Linux can be
configured for larger stack.
Linux needs to be specially configured to forbid a
On 2019-03-10 10:22, Yuriy Sydorov wrote:
FYI on 64-bit Windows the stack size limit is hard coded to 1GB. The
same 1GB limit applies on 32-bit Windows. Probably Linux can be
configured for larger stack.
Linux needs to be specially configured to forbid a larger stack.
But I agree with Jonas, t
On 09.03.2019 14:06, Fabio Luis Girardi wrote:
The datatype that throws this error is this (cef3types.pas:2416):
TCefCompositionUnderlineArray = array[0..(High(Integer) div SizeOf(TCefCompositionUnderline)) - 1] of
TCefCompositionUnderline;
The TCefCompositionUnderline is a record with 20 byt
On 09.03.2019 14:33, Jonas Maebe wrote:
On 09/03/2019 13:06, Fabio Luis Girardi wrote:
Thanks by your feedback. Do you think that should I fill a bug report?
That's up to you.
I think that 2GB on 64 bits a very conservative limit.
2GB stack space on is very large on any platform. Normally
Em Sáb, 9 de mar de 2019 09:34, Jonas Maebe escreveu:
>
>
> r39916
>
Thanks. How fpcef3 isn't my project and I don't understood how it works (I
don't understand why a very large array is needed), I'll switch back to a
previous revision number and wait the FPC 3.2 to be released. After that
I'll
On 09/03/2019 13:06, Fabio Luis Girardi wrote:
Thanks by your feedback. Do you think that should I fill a bug report?
That's up to you.
I think that 2GB on 64 bits a very conservative limit.
2GB stack space on is very large on any platform. Normally the heap is
used for large allocations.
Hi Jonas!
Thanks by your feedback. Do you think that should I fill a bug report?
The datatype that throws this error is this (cef3types.pas:2416):
TCefCompositionUnderlineArray = array[0..(High(Integer) div
SizeOf(TCefCompositionUnderline)) - 1] of TCefCompositionUnderline;
The TCefCompositionU
On 07/03/2019 21:32, Fabio Luis Girardi wrote:
I'm trying to use the FPC 3.2.0 beta + Lazarus 2.0.1 with fpCEF3. But
when I try compile this package with FPC 3.2.0 I got this error:
Error: Local variables size exceeds supported limit
But the same package compiles fine with FPC 3.0.4 and 3.0.5
On 07.03.2019 22:32, Fabio Luis Girardi wrote:
Hi All!
I'm trying to use the FPC 3.2.0 beta + Lazarus 2.0.1 with fpCEF3. But when I try compile this package with FPC 3.2.0 I
got this error:
Error: Local variables size exceeds supported limit
It would be helpful if you provide a code snippet
Hi All!
I'm trying to use the FPC 3.2.0 beta + Lazarus 2.0.1 with fpCEF3. But when
I try compile this package with FPC 3.2.0 I got this error:
Error: Local variables size exceeds supported limit
But the same package compiles fine with FPC 3.0.4 and 3.0.5.
Should I fill a bug report?
Ahh, in ti
13 matches
Mail list logo
