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 no
"break" is a windows built-in. explains the first attempt.
--
Alexander Grotewohl
https://dcclost.com
From: fpc-devel on behalf of Tomas
Hajny via fpc-devel
Sent: Friday, November 27, 2020 11:16:26 AM
To: FPC developers' list
Cc: Tomas Hajny
Subject: Re: [fpc-
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
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
On Thu, Nov 26, 2020 at 11:10 PM Tomas Hajny via fpc-devel
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.
