Reading about you snacking on wine with delicious cheese (experimenting with a new backend) is interesting!
But we want to try something to compile, too.
Is it possible in summer?
Or not before the new year?
For me the compilation time is not really an issue as long as compiling a program don't take an hour or so. I'm playing with C and C++ codes and it take some time to get used to little longer compilation time in comparison with PureBasic, but it's bearable. So I'm willing to sacrifice some compilation time for better program performance overall.
Because of this bug I have to compile +64000 lines of code program with the standalone debugger and let me tell you that it took almost 6 seconds to have the program up and running. I hope Fred, even if is very busy with the new backend, will have this bug sorted out for the next release. But for now when I work on this big project and I need to compile with the debugger I just wait for it.
Best regards
StarBootics
The Stone Age did not end due to a shortage of stones !
majikeyric wrote: ↑Thu May 13, 2021 4:22 am
OMG the execution speed increase is AMAZING !
Yes Indeed ! And this speed improvement make me wonder why the FASM backend should remain after all problems will be worked out about the C backend. Even if the FASM backend remain available probably nobody will use it.
Best regards
StarBootics
The Stone Age did not end due to a shortage of stones !
StarBootics wrote: ↑Thu May 13, 2021 11:35 amAnd this speed improvement make me wonder why the FASM backend should remain after all problems will be worked out about the C backend.
Because the compilation time is much faster in FASM. During development I would prefer a fast as possible compilation time. The fast execution time is preferred for the released version. A compilation time of more than ~10 seconds would be a no go for me.
But of cause, this is only my opinion!
I'm also very happy to see this large improvement in execution time with the C-compiler.
If it can also beat my assembler-only procedures, the future will show.
Yes, this is why I asked how much compilation time the optimization settings added?
Amalgamated Sqlite.c can take almost 30sec depending on situation.
For me, it does not make sense to debug with FASM if C will introduce subtle errors or behavioral changes.
My approach will be to debug with C and -0 optimiziers and then release with the full shebang!
The nice thing about standards is there are so many to choose from. ~ Andrew Tanenbaum
skywalk wrote: ↑Thu May 13, 2021 2:11 pm
Yes, this is why I asked how much compilation time the optimization settings added?
Amalgamated Sqlite.c can take almost 30sec depending on situation.
For me, it does not make sense to debug with FASM if C will introduce subtle errors or behavioral changes.
My approach will be to debug with C and -0 optimiziers and then release with the full shebang!
I guess we will have to wait'N'see how the compilation time will look like.
Best regards
StarBootics
The Stone Age did not end due to a shortage of stones !
BarryG wrote: ↑Fri Mar 26, 2021 12:29 pmI'm hoping the new compiler with the new code base will generate entirely new code patterns that won't be recognized as "malware" anymore.
"The IDE is finally working with the C back-end !"
"[...]All in all, it’s very good news, and we are looking forward to fix the last remaining showstoppers and creating a beta version for all the OS, including may be some new like Raspberry !"