Path: csiph.com!news.swapon.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: GCC vs Clang Date: Wed, 27 Jul 2016 10:04:58 -0700 Organization: None to speak of Lines: 23 Message-ID: References: <5798ceed.3489562@news.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="945944de09706c9b4e29b53c9d2efdc2"; logging-data="27109"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/iCyNtEXvljtuBokqfrZM4" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:kVMSDEh48Lm6Yk2dQRgYeN1slHo= sha1:zlIgD8Fds5bR9hZMaVwF06ByxJo= Xref: csiph.com comp.lang.c:91162 Keith Thompson writes: [...] > It is unfortunate that the compiler and the runtime library did not > agree on the representation of long double. There is a workaround: > defining the macro "__USE_MINGW_ANSI_STDIO" as 1 before including > causes it to use a different implementation of stdio. > (I don't know whether this applies to the long double functions > declared in and .) [...] It occurs to me that configuring gcc to use the Windows native representation for long double would have been a better solution. gcc even has command line options that controls the size of long double. Perhaps the MinGW developers had (or thought they had) good reasons not to do that. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"