I got a fix.

https://bugs.freepascal.org/view.php?id=38129

It's not perfect because CSE becomes less efficient, but it appears to fix the bug.  Someone with more knowledge of this part of the compiler might be able to improve on it in the future. x86_64-win64 and aarch64-linux tests all pass.  I'm not yet sure if it fixes the -O2 bugs reported on aarch64 specifically - those will have to be tested when this fix (or another one) goes live.

Gareth aka. Kit

On 27/11/2020 19:47, J. Gareth Moreton via fpc-devel wrote:

Crumbs, this minor aside has blown up more than the original problem!

To get back on topic, it seems there's a bug with one of the node code generators under -O2 and above.  It's not something I've researched that deeply, but I would like to see it fixed. First though we need to find which node is malfunctioning.

Gareth aka. Kit

On 27/11/2020 19:43, Alexander Grotewohl via fpc-devel wrote:
"break" is a windows built-in. explains the first attempt.

--
Alexander Grotewohl
https://dcclost.com <https://dcclost.com>
------------------------------------------------------------------------
*From:* fpc-devel <fpc-devel-boun...@lists.freepascal.org> on behalf of Tomas Hajny via fpc-devel <fpc-devel@lists.freepascal.org>
*Sent:* Friday, November 27, 2020 11:16:26 AM
*To:* FPC developers' list <fpc-devel@lists.freepascal.org>
*Cc:* Tomas Hajny <xhaj...@hajny.biz>
*Subject:* Re: [fpc-devel] Might need some help with this one
On 2020-11-27 15:34, Bart via fpc-devel wrote:
> On Thu, Nov 26, 2020 at 11:10 PM Tomas Hajny via fpc-devel
> <fpc-devel@lists.freepascal.org> wrote:
>
>> Typing 'break.exe' in cmd.exe _does_ make a difference here (it
>> executes
>> as expected unlike when typing just 'break'). And obviously running
>> break.exe using some other 'shell' (e.g. your preferred OFM ;-) )
>> works
>> as well.
>
> Well, at my machine it did not.
> I also called it from a batchfile (as break.exe) to see if I could
> catch the errorlevel (I let it crash with a division by zero).
> The errorlevel is set, but absolutely no output to screen or pipe.

Understood. Haven't I already mentioned something about MS approach
towards compatibility here recently? :/

-------------------
D:\TEMP>cmd
Microsoft Windows [Version 10.0.18363.1082]
(c) 2019 Microsoft Corporation. Všechna práva vyhrazena.

D:\TEMP>break

D:\TEMP>break.exe
I am Break

D:\TEMP>.\break
I am Break

D:\TEMP>
===================

Tomas
_______________________________________________
fpc-devel maillist  - fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel <https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel>

_______________________________________________
fpc-devel maillist  -fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

_______________________________________________
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Reply via email to