https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111654
--- Comment #4 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Julian Waters from comment #2) > (In reply to Manuel López-Ibáñez from comment #1) > Yeah, I did try submitting it to gcc-patches, but it simply went ignored for > forever, so I decided to submit the patch through the bug system instead, > like others have done. I implemented it as numeric values to avoid inventing > new names for -Woption and because it was easier to implement for a gcc > beginner like myself, so worded warnings are likely to take me longer to > implement Apologies, I was not aware of that. I think it is a good idea to add the link to the mailing list here in bugzilla so it is not lost in the mailing list archive. Unfortunately, gcc does not have any patch tracking system so it is up to submitters to ping patches (the submitter is the one interested in seeing the patch committed). See for example: https://gcc.gnu.org/pipermail/gcc-patches/2023-August/627958.html It may take 4 to 10 pings to get the patch reviewed. It helps sometimes to describe the area the patch touches in the subject. In your case, I would write "[C family]". It helps reviewers if you mention how the patch was tested and also if the patch is attached as plain-text (not as application/*): https://gcc.gnu.org/contribute.html#patches See other suggestions on how to interact with the GCC community here: https://gcc.gnu.org/wiki/Community
