Hello Christopher,

On Sat, Nov 21, 2026 at 10:51:54AM +0000, Christopher Bazley wrote:
> > which refers as a motivation to the author's own proposal
> > (without disclosing the authorship, calling it instead a "draft ISO/IEC")
> >
...
> I wrote the _Optional proposal and the committee draft cited in the
> commit message, WG14 N3951

I am glad that we agree on this point.

> > and also names a second reason: to make tinycc follow SDCC behavior.
> >
> > Neither of those reasons look sufficient to me, especially given that
> > the same person have been active in support of _Optional in SDCC.

> but Philipp Krause led the work in SDCC,
> not me. He proposed adding the qualifier there so SDCC could warn
> about missing null checks:
> 
> https://sourceforge.net/p/sdcc/feature-requests/1003/

Nevertheless, it looks like you have been and are actively involved in the
corresponding implementation of _Optional there, judging from the commits.

Your use of the SDCC project as a reference without disclosing your
involvement there made me uncomfortable.

> SDCC's developers believe that _Optional is the best fit for the
> language and for their compiler.

Those beliefs are not relevant here.
Tinycc is a separate compiler, with different uses, users, developers
and with its own criteria.

> a side-effect of  implementing and testing
> _Optional has been to discover and fix bugs in [...] handling of
> qualified types.

Bug fixing is useful, please do.

But please do not use this as an excuse to enforce new functionality,
at a cost.

Features are easy to add, hard to remove. Tinycc can only stay tiny by
being cautious.

> I believe my commits give a lot of value relative to their size.

Of course you believe in the usefulness of the extension - your brainchild
(I do have full respect for this).

Still, not least for that very reason, your belief is not an argument.

> Yes, N3951 is password-protected. That is annoying, but unfortunately
> the committee manager tells me that ISO's rules require it.

Oh. I did not spot any other encrypted file there in
https://www.open-std.org/JTC1/SC22/WG14/www/wg14_document_log

If the standardizing committee itself does not want the current
proposal to be public, tinycc should hardly be bothered by following a
hidden target, explainable only via yourself.

> There is a bit of a "chicken and egg" problem with how the C committee
> works. The committee asks "Has the feature been deployed in a
> compiler?" whilst compiler maintainers ask "Has the feature been
> approved by the committee?"

This looks almost like as if you were using tinycc to build a case for the
standardizing committee that, given SDCC and tinycc, "multiple compilers
support the proposal's functionality".

Hinting in the commits to authority of "ISO draft" and to SDCC,
without telling about your own stake there, strengthens unfortunately
this impression.

I see your additions as a danger for the direction of the tinycc
project. All of us have to carry the added extra code, for a possible
future language feature which is not even finalized.

You might want to put your changes into your own branch or repository,
to be able to present the compiler support to the committee, without it
looking like tinycc is endorsing it.

( You have apparently a clang fork, why not do the same with tinycc?
  On Sat, Nov 21, 2026 at 04:01:16PM +0000, Christopher Bazley wrote:
  > [...] My Clang fork [...]
)

> My reason for favouring support in TCC itself is that SDCC already
> accepts _Optional.

1. Tinycc was already fully compatible with sources who use _Optional,
via -D_Optional= .

2. SDCC and tinycc are not related to each other except by being
two quite different C compilers.

3. The possible usefulness of interpreting _Optional in the compiler is
known only from your point of view. Until now nobody else on this list
has asked for the extension.

As a compiler user, I do not need nor expect extensive checking of C
code by tinycc. There are other more specific tools for such a purpose.
I need and appreciate tinycc's compactness and speed.

On Sat, Nov 21, 2026 at 04:01:16PM +0000, Christopher Bazley wrote:
> I would be reluctant to revert _Optional from mob because that would
> also have a cost: I currently compile my C projects with TCC; doing so
> has exposed unrelated compiler bugs

Your contribution to bugfixing is conditional on tinycc's upstream
following the specifics of your projects - this is unfortunate.

I think it is fair to accept the loss and thank you for cooperation thus far.

I would appreciate if you revert the changes in mob, beginning with
https://repo.or.cz/tinycc.git/commit/8b58a07b95a637e6d9060b4c26bc0f2e7758f1a4

Regards,
/tccm

_______________________________________________
Tinycc-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to