https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36587
--- Comment #15 from Kaz Kylheku <kkylheku at gmail dot com> --- (In reply to Manuel López-Ibáñez from comment #13) > (In reply to Kaz Kylheku from comment #11) > > I deployed that change to large team of developers, and the toolchain with > > that change went to customers also. The warning caught problems that were > > fixed and didn't appear to break anything. > > If the patch were to be upstreamed, it will be reviewed, regression tests > would be added to make sure it doesn't silently break, and your customers > could update to newer versions of GCC without losing the warning. In April 2020 I created a patch for the GNU C Preprocessor, with documentation, test cases and everything. I submitted it to the GCC Patches mailing list, exactly as comments in this ticket from 2015 advised me I should have done for this item back in 2008. I received absolutely no replies; not even to reject the submission. I "pinged" it a number of times, to no avail. The four year anniversary is coming up; I'm going to ping again. Then if I'm still ignored, one last time in April 2025.
