Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: Why does C allow structs to have a tag?
Date: Fri, 30 Jul 2021 14:17:08 -0700
Organization: None to speak of
Lines: 31
Message-ID: <87r1ffcxij.fsf@nosuchdomain.example.com>
References: <s9iea5$n5c$1@dont-email.me> <87sfzzgr72.fsf@nosuchdomain.example.com> <GvdMI.119844$h8.84268@fx47.iad> <sdrqho$qta$1@dont-email.me> <nCeMI.8803$Dk6.4825@fx20.iad> <sds1rk$pvj$1@dont-email.me> <1mgMI.17475$6j.16299@fx04.iad> <sdsme0$2r6$1@dont-email.me> <87zgu6f367.fsf@nosuchdomain.example.com> <sdsvto$jqt$1@dont-email.me> <87v94tg8sw.fsf@nosuchdomain.example.com> <sdtugu$an9$1@dont-email.me> <87mtq5f92k.fsf@nosuchdomain.example.com> <sduhq4$3ll$1@dont-email.me> <87im0tf2rn.fsf@nosuchdomain.example.com> <sduqoh$np9$1@dont-email.me> <87a6m5f0j9.fsf@nosuchdomain.example.com> <sdusob$h8b$1@dont-email.me> <se15br$1pog$1@gioia.aioe.org> <874kcbekgs.fsf@nosuchdomain.example.com> <se1g4e$1635$2@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: reader02.eternal-september.org; posting-host="a2365495de71cceec5c7a6c9f6767045"; logging-data="1850"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18k6rJSbvKXcu543hemaLTt"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Cancel-Lock: sha1:vgsPcqrqiAsYzIK19b4q2hy21eA= sha1:53HTMdVlBpEgrNUFuiBi4TboU6s=
Xref: csiph.com comp.lang.c:162141

Manfred <noname@add.invalid> writes:
> On 7/30/2021 8:16 PM, Keith Thompson wrote:
>> Manfred <noname@add.invalid> writes:
>> [...]
>>> Yes, if you use gcc under Windows you are actually importing a chain
>>> of dependencies that you don't want to bother with - That's the reason
>>> I only use gcc on Linux.
>> [...]
>> Cygwin is one way to use gcc under Windows, but it's not the only
>> one.
>> There are other implementations on Windows that include gcc but are not
>> connected to Cygwin.  See for example mingw-w64 (which seems to have
>> some relationship to Cygwin, but I'm not clear on the details).
>
> Still I believe that none of them is officially supported by the gcc team.

Right, gcc and glibc are separate projects, both under the GNU umbrella.
I'm unsure of the relationship between newlib and GNU (a quick look at
its README and MAINTAINERS files was a bit confusing), but that doesn't
really matter for most purposes.

Of course the whole point of gcc is for it to be usable as a compiler.
If some change in gcc caused it not to work with glibc, that would be a
bug that would presumably be addressed with a high priority, and vice
versa.  (A similar bug that affects gcc working together with a
Microsoft-specific runtime library might be given a lower priority.)

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips
void Void(void) { Void(); } /* The recursive call of the void */