Am 29.04.2023 um 19:48 schrieb geneb via fpc-other:
On Sat, 29 Apr 2023, Bernd Oppolzer via fpc-other wrote:
This may be slightly off-topic, but I can tell you some facts about
my Stanford Pascal compiler,
which runs
- native on z Mainframe machines (which may count as a RISC machine
OF CODE GENERATED, 8.24 SECONDS IN POST_PROCESSING.
EXEC PASLINK PASCAL1
Ready; T=17.71/27.02 18:17:06
Kind regards
Bernd
Am 29.04.2023 um 18:15 schrieb Bernd Oppolzer:
This may be slightly off-topic, but I can tell you some facts about my
Stanford Pascal compiler,
which runs
- native on z
LER, OPPOLZER VERSION OF 2023.03
Compiler Summary
No Errors, no Warnings.
26058 LINE(S) READ, 243 PROCEDURE(S) COMPILED,
75130 P_INSTRUCTIONS GENERATED, 13.55 SECONDS IN COMPILATION.
*** EXIT Aufruf mit Parameter = 0 ***
HTH, kind regards
Be
Am 26.12.2016 um 10:31 schrieb Alexander Stohr:
Am 2016-12-25 um 21:42 schrieb Bernd Oppolzer:
Thank you for your feedback.
Thank you for your kind answers.
You're welcome; I'm happy to meet someone who is interested in my work :-)
BTW, I had to remove some sort of self check from
Am 24.12.2016 um 12:50 schrieb Mark Morgan Lloyd:
On 24/12/16 11:30, Bernd Oppolzer wrote:
chars in
the (character) P-Code file had to be converted to character
constants; all
places where character A - for example - was represented as numeric 193
(which is EBCDIC 'A') had to be found
). The compiler compiles itself
in 2 to 3 seconds on both platforms (using a laptop running
Windows 10 or the Hercules emulator; the laptop is not brand new).
You find some stories about my efforts of the last years and
months on my web site:
http://bernd-oppolzer.de/job9.htm
There are still some
to contribute and *has* the
time, I strongly suggest letting him do it. After all what damage
could happen? It could only get better, I doubt it can get worse.
Therefore I support this request.
Bernd
___
fpc-other maillist - fpc-other@lists.freepascal.org
http
