Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Tim Rentsch Newsgroups: comp.lang.c Subject: Re: How many wide characters may mbstowcs store? Date: Tue, 23 Jun 2020 05:35:06 -0700 Organization: A noiseless patient Spider Lines: 37 Message-ID: <86sgemhsed.fsf@linuxsc.com> References: <86mu6exxpw.fsf@linuxsc.com> <86k112u2kx.fsf@linuxsc.com> <86tv02ss0m.fsf@linuxsc.com> <86h7vyrqzf.fsf@linuxsc.com> <4VhhmiNkewUzTX9GU@bongo-ra.co> <86ftbcp2yl.fsf@linuxsc.com> <5536866b-2ddf-4095-ad9d-4d2317bff0e9@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="8b9803fe1fafcf574686fbce0cef2b4f"; logging-data="25627"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/+KJid0kc1zXCsY6FYNvi8l6DVPBtOLbo=" User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux) Cancel-Lock: sha1:nXPTV+PK6lq6tWO+M8NG7BoQWZI= sha1:OIjNGoDJt7jMVeskBLxf9iuTcQQ= Xref: csiph.com comp.lang.c:152891 James Kuyper writes: > On Wednesday, June 3, 2020 at 11:46:21 AM UTC-4, Tim Rentsch wrote: > >> Spiros Bousbouras writes: >> >>> On Fri, 29 May 2020 21:23:00 -0700 >>> Tim Rentsch wrote: >>> >>>> Spiros Bousbouras writes: >>>> >>>>> On Tue, 26 May 2020 07:14:01 -0700 >>>>> Tim Rentsch wrote: >>>>> >>>>>> I still think a bug report should be filed against gcc >>>>>> itself. If gcc is going to allow outside forces (meaning >>>>>> ones completely outside its control) to alter its behavior >>>>>> so it is no longer conforming, there should at least be an >>>>>> option to prevent such alterations. > > As a user, you have that option: install a version of gcc that > was not so patched. Apparently I haven't made myself clear. I see no reason to suppose that gcc has been patched by anyone outside the gcc developer group. It seems more likely that they put in a capability for enabling these transformations, triggered by a setting in library header files. The people who put together the Ubuntu distribution simply enabled the setting in the library headers; they didn't any changes to gcc itself. So gcc should have a way of turning off that outside interference, since they are the ones who enabled it in the first place. Disclaimer: I have no direct knowledge of who made what changes to gcc source. I am simply making an educated guess based on whatever miscellaneous evidence has been discovered during my various perusings.