Re: [fpc-devel] Internal error 2018062911

2019-11-11 Thread J. Gareth Moreton
All fixed, https://bugs.freepascal.org/view.php?id=36299 Gareth aka. Kit ___ fpc-devel maillist - fpc-devel@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Internal error 2018062911

2019-11-11 Thread C Western
Gareth - It is indeed linux 64 bit. I use: make distclean DEBUG=1 install NOGDB=1 NOGDBMI=1 GDBMI=1 PREFIX=/home/me/usr64 FPC=/home/me/fpc/bootstrap/ppcx64 in the fpcsrc directory which gives: make -C fpcsrc distclean make[1]: Entering directory '/home/me/fpc/trunk/fpcsrc' make -C compiler

Re: [fpc-devel] Internal error 2018062911

2019-11-11 Thread J. Gareth Moreton
Hi Colin, So unfortunately I haven't been able to reproduce the issue under Windows, which leads me to believe this issue only crops up when building for Linux.  If you can get on that bug report and tell me what command you're using to build everything (my experience with Linux is not very

Re: [fpc-devel] Internal error 2018062911

2019-11-11 Thread J. Gareth Moreton
Aah, scratch that last question.  The '-gl' flag is more important. On 11/11/2019 20:59, J. Gareth Moreton wrote: Ooh, thats an oversight on my part.  The internal error is raised as part of the jump optimisations if it finds something other than a label or an alignment hint - I didn't think

Re: [fpc-devel] Internal error 2018062911

2019-11-11 Thread J. Gareth Moreton
Ooh, thats an oversight on my part.  The internal error is raised as part of the jump optimisations if it finds something other than a label or an alignment hint - I didn't think to check for debug markers.  I'll get around to that right now.  In the meantime, can you raise a bug report over

[fpc-devel] Internal error 2018062911

2019-11-11 Thread C Western
I am seeing internal error 2018062911 with trunk r43441 and above. This may be the result of building with DEBUG on, but this configuration normally works fine for me. Colin External command "/home/me/fpc/trunk/fpcsrc/compiler/ppcx64 -Tlinux -FUfcl-xml/units/x86_64-linux/

Re: [fpc-devel] Capturing addresses

2019-11-11 Thread Marc Weustink via fpc-devel
Jonas Maebe wrote: Hi, Does anyone know what the accepted/excepted behaviour is regarding the capture of addresses of var/out/const-by-address/constref parameters? For example: var g: longint; p: plongint; procedure test(var l: longint); begin p:=@l; end; begin test(g); end.

Re: [fpc-devel] inline... and philosophy

2019-11-11 Thread Marco van de Voort
Op 10/11/2019 om 16:02 schreef J. Gareth Moreton: This message chain has proven to be a lot more educational and insightful than I would have given it credit for.  Thanks everybody! I know a lot of the time, the size of binaries is just an illusion, along with unfair comparisons with GCC (a