Hi
On which platform? When I compile the attached tt.pp file with -gw4
-Clfsanitize=address (LLVM 13, Debian 11, x86-64) and then run it, I
get the output in tt.txt. It includes line information.
You could try lldb instead of gdb, although gdb should also be able to
handle debug information g
On 15/08/2023 17:24, Benito van der Zander via fpc-pascal wrote:
Hi
-Clflto -Clflto-no-system -k-fuse-ld=gold -k-plugin=/path/to/LLVMgold.so
that helped, but I have to do it without -Clflto-no-system, or it gives
an error
That was a typo, it's -Clfltonosystem. But it doesn't matter if the
Hi
-Clflto -Clflto-no-system -k-fuse-ld=gold -k-plugin=/path/to/LLVMgold.so
that helped, but I have to do it without -Clflto-no-system, or it gives
an error
Then I could run my unit tests:
FPC alone: 25 seconds
LLVM: 21 seconds
LLVM LTO: 20 seconds
does not seem to matter much
Cheers,
Be
Jonas Maebe via fpc-pascal wrote:
See e.g. the explanation of "data dependency barrier" at
https://www.sobyte.net/post/2022-08/cpu-cache-and-memory-barriers/ . In
Interesting stuff to read.
Regards,
Adriaan van Os
___
fpc-pascal maillist - fpc-
Hi all,
Not sure if this is a bug, but I'm seeing some strange behaviour with
encodeURLElement on the latest build from source.
See attached file url.pas.
I'm using Debian 12.
Regards,
David Connolly
{$mode delphi}
{$H+}
{$codepage utf8}
program url;
uses
cwstring,
fphttpclient;
var
ansi :
Jonas Maebe via fpc-pascal schrieb am
Mo., 14. Aug. 2023, 21:02:
> On 14/08/2023 18:19, denisgolovan via fpc-pascal wrote:
> > Now we have "volatile" intrinsic for assignments in place, I'd like to
> ask for another clarification.
>
> Just to make sure given your questions below: using volatile i
