Hello Christopher, On Fri, Nov 20, 2026 at 09:12:47PM +0000, Christopher Bazley wrote: > I pushed 205f264b9e01 to mob earlier. It adds -Wnull-to-nonoptional, > which warns when a null pointer constant is implicitly converted to a > pointer whose target type lacks the _Optional qualifier. ... > off by default because such conversions are commonplace
Indeed. This is, as Michael Ackermann also seems to point out, already a reason to hesitate about whether the addition would be worth it. Tinycc can hardly aim to include all potentially useful diagnostics, because each one adds the size and complexity. > Annex B of ISO/IEC DTS 26716 (WG14 N3951) lists this conversion as one > for which an implementation can usefully warn. Do you have a readable link? The document at https://www.open-std.org/JTC1/SC22/WG14/www/docs/n3951.pdf "2026/08/16 Bazley, _Optional Technical Specification (Committee Draft)" looks password protected, which other documents which I checked in the log https://www.open-std.org/JTC1/SC22/WG14/www/wg14_document_log are not. Before adding an implementation it is crucial to know _what_ it is supposed to correspond in the standard. For the moment there seems to exist only your own standardization proposal, as above. According to the log the committee had some concerns about the proposal. Non-standard/unstable features are hardly reasonable to support. > The compiler changes are small Still, it has grown 25 lines plus about a hundred lines in tests and documentation to take care of, if the feature changes. It the feature does not end up in the standard, the corresponding code in tinycc becomes a source of confusion. I would strongly suggest to keep your proposed addition to tinycc as a patch available separately but not as a part of the tinycc project, at least until the feature is standardized. My 2 cents as a tinycc user. Friendly, /tccm _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
