Can /my/ AI help me with pascal coding?

[Graeme]

Port QBE (Quick Back End) and PCL (Portable Code Language) to FPC. 

what do you mean by porting QBE to FPC? As a new FPC code generation backend? QBE is already very easy to use. I'm using is as my Blaise compiler backend. Way, way easier to implement than LLVM, but with the downside that Windows is not supported. I'll eventually implement a LLVM backend in Blaise too.

among other things it would also open the door to using FPC as a compiler development tool.

Again not sure what you mean here. FPC was my bootstrap compiler when I started the Blaise Compiler project. But since I managed self-hosting state, I don't need FPC any more.
 

[440bx]

* PCL?

Good question! one I didn't expect to have to answer.  The author has been making changes and it looks like the PCL backend (PCL8) has become part of his C compiler (I could be wrong about that, actually, I really hope I am wrong about that), bottom line: I have to figure out what's going on before I can give you a solid answer. 

[440bx]

@440bx,

Port QBE (Quick Back End) and PCL (Portable Code Language) to FPC.

I will give consideration to it.

Wondering what are the URLs?
* https://c9x.me/compile/
* PCL?

Consider my request to be for QBE only because getting a PCL that is portable to Pascal will take more time than I anticipated.

Having an FPC version of QBE would be extremely useful.

[schuler]

While the AI coding continues, I would like to share this link:
https://github.com/joaopauloschuler/pas-sqlite3/blob/main/src/tests/DiagSampleProg.pas

wish every AI happy pascal coding

[440bx]

@schuler,

very nice and very useful.  thank you!

[schuler]

Some commands are already working in the CLI interface (see readme):
https://github.com/joaopauloschuler/pas-sqlite3

[cdbc]

Hi
Cool, I've just returned from holiday in sunny Glücksburg-Germany and I'll have to get back in the race... Will test - Thanks mate.
Regards Benny

[schuler]

@cdbc,
It is still a work in progress. It is still buggy. It is probably too early for real testing. But you can compile and try if you are curious.

[valdir.marcos]

Port QBE (Quick Back End) and PCL (Portable Code Language) to FPC. 

what do you mean by porting QBE to FPC? As a new FPC code generation backend? QBE is already very easy to use. I'm using is as my Blaise compiler backend. Way, way easier to implement than LLVM, but with the downside that Windows is not supported. I'll eventually implement a LLVM backend in Blaise too.

among other things it would also open the door to using FPC as a compiler development tool.

Again not sure what you mean here. FPC was my bootstrap compiler when I started the Blaise Compiler project. But since I managed self-hosting state, I don't need FPC any more.

I am curious about your Blaise Compiler Project. Could you talk about it a bit more?

[440bx]

Port QBE (Quick Back End) and PCL (Portable Code Language) to FPC. 

what do you mean by porting QBE to FPC?

I mean porting it from C to FPC.

[schuler]

Just a bit of food for thought, once I stabilize pas-sqlite3.53, comes the question: What should I do next? These are some ideas:

• Go back to pas-core-math: We have 83 functions there that can be independently optimized. So, there are 83 independent optimization problems. And/Or, I could integrate pas-core-math 32 bits into https://github.com/joaopauloschuler/neural-api so I will have faster neural networks specially on linux.
• Integrate pas-sqlite3 into https://github.com/joaopauloschuler/dbdesigner-fork for Lazarus although dbdesigner-fork is not yet stable.
• Integrate https://github.com/joaopauloschuler/pas-bzip2 into pas-sqlite3.
• Once pas-sqlite3 is stable, I could fork pas-sqlite3 and add features to pas-sqlite3 that we miss diverging from the original implementation. We could add features that exist in major databases and do not yet exist in pas-sqlite3.
• Try to improve the FPC optimizer… Maybe, introducing optimizations originally developed to https://github.com/joaopauloschuler/neural-api.
• Port more projects from C to FPC.

Anyway, my capacity to invest in open source projects has limits. This is to share thoughts only.

[ALLIGATOR]

I would vote for fixing bugs in FPC's code generation. Fixing bugs related to generics, absolutes, and other language-related issues, and adding tests

Next, improving optimizations and adding tests

[valdir.marcos]

Just a bit of food for thought, once I stabilize pas-sqlite3.53, comes the question: What should I do next? These are some ideas:

• Go back to pas-core-math: We have 83 functions there that can be independently optimized. So, there are 83 independent optimization problems. And/Or, I could integrate pas-core-math 32 bits into https://github.com/joaopauloschuler/neural-api so I will have faster neural networks specially on linux.
• Integrate pas-sqlite3 into https://github.com/joaopauloschuler/dbdesigner-fork for Lazarus although dbdesigner-fork is not yet stable.
• Integrate https://github.com/joaopauloschuler/pas-bzip2 into pas-sqlite3.
• Once pas-sqlite3 is stable, I could fork pas-sqlite3 and add features to pas-sqlite3 that we miss diverging from the original implementation. We could add features that exist in major databases and do not yet exist in pas-sqlite3.
• Try to improve the FPC optimizer… Maybe, introducing optimizations originally developed to https://github.com/joaopauloschuler/neural-api.
• Port more projects from C to FPC.

Anyway, my capacity to invest in open source projects has limits. This is to share thoughts only.

I would vote for fixing bugs in FPC.

[schuler]

Fixing FPC bugs: 2 votes so far. Thank you for the votes.

I attached an image with pas-sqlite3 progress.

[cdbc]

Cool, quite a job right? Nice to see progress =^
I'll vote for fixing FPC-bugs, so that we can move forward with compiler-team 
Thanks mate & regards
Benny