Re: [fpc-devel] Might need some help with this one

2020-11-27 Thread J. Gareth Moreton via fpc-devel 

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 

*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-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
>  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 



___
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

Re: [fpc-devel] Might need some help with this one

2020-11-27 Thread Alexander Grotewohl via fpc-devel 
"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-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
>  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
___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel

Re: [fpc-devel] Might need some help with this one

2020-11-27 Thread Tomas Hajny via fpc-devel 

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. 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

Re: [fpc-devel] Might need some help with this one

2020-11-27 Thread Bart via fpc-devel 
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.

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.

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