Richard Biener <richard.guent...@gmail.com> writes: > On Mon, Oct 10, 2022 at 5:32 PM Gaius Mulley via Gcc-patches > <gcc-patches@gcc.gnu.org> wrote: >> >> >> Here are the latest modula-2 front end patches for review. >> The status of the patches and their contents are also contained at: >> >> https://splendidisolation.ddns.net/public/modula2/patchsummary.html >> >> where they are also broken down into topic groups. >> >> In summary the high level changes from the last posting are: >> >> * the driver code has been completely rewritten and it is now based >> on the fortran driver and the c++ driver. The gm2 driver adds >> paths/libraries depending upon dialect chosen. >> * the linking mechanism has been completely redesigned >> (As per >> https://gcc.gnu.org/pipermail/gcc-patches/2022-May/595725.html). >> Objects can be linked via g++. New linking options >> are available to allow linking with/without a scaffold. >> * gcc/m2/Make-lang.in (rewritten). >> * gm2tools/ removed and any required functionality with the >> new linking mechanism has been moved into cc1gm2. >> >> The gm2 testsuite has been extended to test project linking >> options. > > Thanks for these improvements!
the front end feels alot cleaner now! > The frontend specific parts are a lot to digest and I think it isn't > too important to wait for the unlikely event that all of that gets a > review. I'm trusting you here as a maintainer and also based on the > use of the frontend out in the wild. I've CCed the other two RMs for > their opinion on this. > > I hope to get to the driver parts that I reviewed the last time, I'd > appreciate a look on the runtime library setup by somebody else. > > I think it's important to get this (and the rust frontend) into the tree > before > Christmas holidays so it gets exposed to the more weird treatment of some > of our users (build wise). This way we can develop either a negative or > positive list of host/targets where to disable the new frontends. great news thanks - yes this makes sense, regards, Gaius
