https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105101
--- Comment #14 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- @Michael: Now that gcc 12 is out of the door, I would suggest we try to get your code into the gcc tree for gcc 13. It should follow the gcc style guidelines, which is quite trivial to do: Comments should be in /* - */ format, and clang-format --style=gnu does the rest. (If you prefer, I can also handle that). Regarding copyright, you can either assign it to the FSF (which would take a bit) or, probably easier, you can use the Signed-off-by: tag as per https://gcc.gnu.org/contribute.html#legal . You would then submit the patch to gcc-patc...@gcc.gnu.org; if you prefer, I can also help a bit with the style issues (ChangeLog etc) for that. It would then be reviewed and, if any problems identified are fixed, applied - which I can also do. How does that sound?
