alf
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 v
wrote:
> "break" is a windows built-in. explains the first attempt.
> --
> Alexander Grotewohl
> https://dcclost.com [1]
> -
> FROM: fpc-devel on behalf of Tomas Hajny via fpc-devel
> SENT: Friday, November 27, 2020 11:16:26 AM
> TO: FPC deve
.com <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
bject: 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
>&g
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.
On 2020-11-26 20:17, Bart via fpc-devel wrote:
On Thu, Nov 26, 2020 at 6:52 PM Jonas Maebe via fpc-devel
wrote:
"break" is probably a command that's recognised by the cmd shell.
Yes it is:
C:\Users\Bart>help break
Sets or Clears Extended CTRL+C checking on DOS system
This is present for Comp
Okay, so I have to specify "-MObjfpc -Sh" to get it to compile due to
what the code uses, and the bug still requires the use of -O2 to
appear. However... "fpc -MObjfpc -Sh -O2 -Ooregvar -alr -sr breakp.pp"
produces a bad binary.
I removed the register comments so it's clearer:
...
# [11]
On Thu, Nov 26, 2020 at 6:52 PM Jonas Maebe via fpc-devel
wrote:
> "break" is probably a command that's recognised by the cmd shell.
Yes it is:
C:\Users\Bart>help break
Sets or Clears Extended CTRL+C checking on DOS system
This is present for Compatibility with DOS systems. It has no effect
unde
Hi,
On 26.11.2020 17:34, J. Gareth Moreton via fpc-devel wrote:
Hi everyone,
So a couple of people have reported that -O2 sometimes produces bad code under x86_64. So far it seems isolated to that
CPU.
https://bugs.freepascal.org/view.php?id=38129
After my own investigations with the attac
Hah, that's the reason! Thanks Jonas. Crisis averted.
Now for the original problem...
Gareth aka. Kit
On 26/11/2020 17:52, Jonas Maebe via fpc-devel wrote:
On 26/11/2020 16:34, J. Gareth Moreton via fpc-devel wrote:
P.S. Also, there seems to be a strange, unrelated glitch. If I rename
the f
On 26/11/2020 16:34, J. Gareth Moreton via fpc-devel wrote:
> P.S. Also, there seems to be a strange, unrelated glitch. If I rename
> the file to "break.pp" and change the program name to "break" (from
> breakp), the compiled binary doesn't seem to write output (or it
> immediately exits - can't t
That is very peculiar, especially given that Delphi has the same
problem! I wonder what's causing that.
Going back to the problem at hand though... seems we have bad code being
generated in places on x86_64, but it's not in the peephole optimizer
for once!
Gareth aka. Kit
On 26/11/2020 17:
On Thu, Nov 26, 2020 at 6:25 PM Bart wrote:
> program break;
> {$apptype console}
>
> begin
> writeln('I am Break');
> end.
>
> Compiles with fpc 3.2.0 and Delphi 7.
> Outputs nothing at all with both compilers
>
> If I run it inside GDB
> Delphi 7 of fpc:
> Starting program: C:\Users\Bart\
On Thu, Nov 26, 2020 at 5:00 PM J. Gareth Moreton via fpc-devel
wrote:
program break;
{$apptype console}
begin
writeln('I am Break');
end.
Compiles with fpc 3.2.0 and Delphi 7.
Outputs nothing at all with both compilers
If I run it inside GDB
Delphi 7 of fpc:
Starting program: C:\Users\B
Technically it isn't a reserved word, or at least not a keyword. Either
way the compiler allows it, but the result is peculiar. It probably
shouldn't be allowed in that case.
Gareth aka. Kit
On 26/11/2020 15:58, Bart via fpc-devel wrote:
On Thu, Nov 26, 2020 at 4:34 PM J. Gareth Moreton via
On Thu, Nov 26, 2020 at 4:34 PM J. Gareth Moreton via fpc-devel
wrote:
> P.S. Also, there seems to be a strange, unrelated glitch. If I rename
> the file to "break.pp" and change the program name to "break" (from
> breakp), the compiled binary doesn't seem to write output (or it
> immediately ex
Hi everyone,
So a couple of people have reported that -O2 sometimes produces bad code
under x86_64. So far it seems isolated to that CPU.
https://bugs.freepascal.org/view.php?id=38129
After my own investigations with the attached code, the problem still
occurs even if the peephole optimizer
18 matches
Mail list logo
