On Fri, 20 Nov 2026 21:12:47 +0000, Christopher Bazley wrote:
> Dear TCC developers,
>
> 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. The warning
> is off by default because such conversions are commonplace;
> Thanks,
> Christopher
>
> 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. The warning
> is off by default because such conversions are commonplace;
> Thanks,
> Christopher
Hi Christopher.
"_Optional" is still not in a public working draft for the upcoming C2y standard,
just on the Agenda of the latest WG14 meeting (which was 16.11.2026 - 20.11.2026).
just on the Agenda of the latest WG14 meeting (which was 16.11.2026 - 20.11.2026).
The Editor's Report is not online yet and the proposal is password protected.
Neither clang nor gcc have the mentioned warning switch.
Neither clang nor gcc have the mentioned warning switch.
In addition, tcc should be small and fast.
Is this new C2y feature (when it was accepted for inclusion this week)
Is this new C2y feature (when it was accepted for inclusion this week)
the right feature to be implemented in current tcc?
Currend tcc is a release candidate.
When will we get a release, when new features are added again and again?
When will we get a release, when new features are added again and again?
I would prefer to revert anything related to "_Optional" and the new warning switch in current tcc now.
--
Regards ... Detlef
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
