Path: ...!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.lang.c
Subject: Re: Baby X is bor nagain
Date: Sun, 30 Jun 2024 01:49:26 -0700
Organization: A noiseless patient Spider
Lines: 70
Message-ID: <86cynyddd5.fsf@linuxsc.com>
References: <v494f9$von8$1@dont-email.me> <v5cblg$11q0j$1@dont-email.me> <gEieO.108089$ED9b.25598@fx11.iad> <20240625113616.000075e0@yahoo.com> <mUzeO.141609$Cqra.55051@fx10.iad> <v5elql$1jmii$1@dont-email.me> <m3BeO.24907$Gurd.16179@fx34.iad> <v5empd$1jndv$2@dont-email.me> <v5eph4$1k6a9$1@dont-email.me> <87ed8jnbmf.fsf@bsb.me.uk> <v5jhls$2m7np$1@dont-email.me> <v5jm32$2nqvp$1@dont-email.me> <v5k3v2$2qllm$1@dont-email.me> <v5kfst$2svt3$1@dont-email.me> <v5kmlm$2u918$1@dont-email.me> <20240627201830.854@kylheku.com> <v5m2nl$39qob$3@dont-email.me> <20240628032211.403@kylheku.com> <v5p4rv$3u92q$1@dont-email.me> <86le2ndajg.fsf@linuxsc.com> <v5pbn7$75a$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Date: Sun, 30 Jun 2024 10:49:26 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="f8122076af5546f7640a872624b0271f";
	logging-data="470565"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/ztY8R96DEYKPWoNC+ra5Rt8BNa+Vn40I="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:CSjqJOGc6p5ekiJNNv1SAHgxdZI=
	sha1:CT7LX2dm0NVxtyF+52FzaOz1zEI=
Bytes: 3999

bart <bc@freeuk.com> writes:

> On 29/06/2024 16:38, Tim Rentsch wrote:
>
>> bart <bc@freeuk.com> writes:
>>
>>> On 28/06/2024 11:26, Kaz Kylheku wrote:
>>>
>>>> On 2024-06-28, bart <bc@freeuk.com> wrote:
>>>>
>>>>> On 28/06/2024 04:23, Kaz Kylheku wrote:
>>>>>
>>>>>> On 2024-06-27, bart <bc@freeuk.com> wrote:
>>>>>>
>>>>>>> And for most of /my/ compiles, the code produced by gcc-O0 is
>>>>>>> fast enough.  It also about the same speed as code produced by
>>>>>>> one of my compilers.
>>>>>>>
>>>>>>> So I tend to use it when I want the extra speed, or other
>>>>>>> compilers don't work, or when a particular app only builds
>>>>>>> with that compiler.
>>>>>>>
>>>>>>> Otherwise the extra overheads are not worth the bother.
>>>>>>
>>>>>> How good are your diagnostics compared to GCC -O2, plus -Wall
>>>>>> and -W?
>>>>>
>>>>> Using products like tcc doesn't mean never using gcc.
>>>>> (Especially on Linux where you will have it installed anyway.)
>>>>>
>>>>> You can use the latter to do extra, periodic checks that the
>>>>> simpler compiler may have missed, or to produce faster production
>>>>> builds.
>>>>>
>>>>> But gcc is not needed for routine compilation.
>>>>
>>>> Catching common bugs in routine compilation is better than once
>>>> a month.
>>>>
>>>> You could be wasting time debugging something where GCC would have
>>>> told you right away you have something uninitialized or whatever.
>>>
>>> Let's take the C program below.  It has 4 things wrong with it,
>>> marked with comments.
>>>
>>> [...]
>>
>> People are never going to take you seriously as long as
>> you keep offering what are obviously strawman arguments,
>> and especially ones where you know better but pretend
>> that you don't.
>
> You've perhaps missed my main point,

I didn't.

> You've probably also missed my secondary point,

I didn't.

> I've also learnt something interesting.  Which is that whatever the
> current version of gcc does is always right, and I'm always wrong if I
> suggest it should be any different.

You still haven't learned the most important thing.  Many or
most of the people responding to you are offering constructive
advice.  For some reason you either don't hear or don't heed
the advice but instead take it as a personal attack.  As long
as you keep doing that no one is going to care about what you
have to say.