[fpc-pascal] WideStringToUCS4String optimization

2019-10-11 Thread Alexey Tor.
Hi {$ifdef FPC_HAS_FEATURE_DYNARRAYS} procedure UCS4Encode(p: PWideChar; len: sizeint; out res: UCS4String);   var     i, reslen: sizeint;     w: longint;   begin     reslen:=0;     i:=0;     { calculate required length } this func loops over the buffer 2 times. 1) find len in UCS4 chars, 2)

[fpc-pascal] FPC 3.3 trunk error with CudaText

2019-10-11 Thread AlexeyT
Win10 x32, Free Pascal Compiler version 3.3.1-r43163 [2019/10/11] for i386 After installing FPC trunk (via fpcupdeluxe), I cannot run CudaText from IDE. Also dont run from console: The application has failed to start because its side-by-side configuration is incorrect. Please see the

Re: [fpc-pascal] Floating point exception not always caught on Linux i386.

2019-10-11 Thread Bernd Mueller
On 10/11/19 10:51 AM, Bart wrote: See https://www.freepascal.org/docs-html/current/prog/progsu69.html#x76-750001.2.69 sorry, I forgot to mention, that I checked with {$SAFEFPUEXCEPTIONS ON}, but it did not change the behavior. Regards, Bernd. ___

Re: [fpc-pascal] Floating point exception not always caught on Linux i386.

2019-10-11 Thread Zamrony P. Juhara via fpc-pascal
I use FPC 3.0.4 on Ubuntu 16.04 I get same behavior after compile it with ppc386. 64bit binary executable run OK Zamrony P. Juhara Fano Framework, Free Pascal web application framework https://fanoframework.github.io On Friday, October 11, 2019, 4:39:38 PM GMT+8, Bernd Mueller wrote:

Re: [fpc-pascal] Floating point exception not always caught on Linux i386.

2019-10-11 Thread Bart
On Fri, Oct 11, 2019 at 10:39 AM Bernd Mueller wrote: > FPC 3.0.4, Linux i386 > > the following program should catch the floating point exception > (always), but crashes on the fourth call to the procedure Run: See https://www.freepascal.org/docs-html/current/prog/progsu69.html#x76-750001.2.69

[fpc-pascal] Floating point exception not always caught on Linux i386.

2019-10-11 Thread Bernd Mueller
Hello, FPC 3.0.4, Linux i386 the following program should catch the floating point exception (always), but crashes on the fourth call to the procedure Run: program test; {$mode objfpc}{$H+} procedure Run; var r: Real; i: Integer; begin i:= 1; try r:= i / 0.0; except