> onlineaet <[email protected]> wrote > > > > > > I am developing a new language, AET, based on gcc 15.2.
There are several issues, the technical ones and the legal ones. Technically I suggest to write a parser and use https://gcc.gnu.org/onlinedocs/jit/ for the back end. Legally I have no idea, but I tend to guess that it won't be easy to have your new (non standard) language inside the GCC compiler itself. Once you wrote your parser (ie front-end) and use libgccjit you profit of the many millions of lines of code for code generation. I tend to believe that you will need to have many thousands of users, and millions of lines of open source software coded by them in AET to have your compiler accepted inside GCC itself. Another alternative is to generate C code and have it compiled by GCC. Being French, I could be wrong. NB. My current open source project (C++ code GPL licensed is an inference engine, see refpersys.org) PS. I obviously recommend using your real first and last name (not a pseudo like onlineaet) when communicating on this and others mailing lists. -- Basile STARYNKEVITCH basile AT starynkevitch DOT net 8 rue de la Faïencerie http://starynkevitch.net/Basile/ 92340 Bourg-la-Reine https://github.com/bstarynk France https://github.com/RefPerSys/RefPerSys https://orcid.org/0000-0003-0908-5250
