From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Peter Dyballa <Peter_Dyballa@web.de>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Configuring GCC 10.3 on PPC Mac OS X 10.4.11/Tiger for build reveals flaws in configure scripts
Date: Thu, 1 Dec 2022 08:22:28 +0000 [thread overview]
Message-ID: <CAH6eHdTS4U8_Pd+znHo6Su=Y4F3MMgsMe=96JZv+a+VPS41Kqw@mail.gmail.com> (raw)
In-Reply-To: <D1043E80-0574-456C-A248-537540227820@Web.DE>
[-- Attachment #1: Type: text/plain, Size: 1940 bytes --]
On Wed, 30 Nov 2022, 23:09 Peter Dyballa, <Peter_Dyballa@web.de> wrote:
> Hello!
>
> Here is my evaluation from building GCC 10.4
>
It's unlikely anybody is very interested in gcc-10 as there will only be
one more release from that branch, and most of these are just harmless
cases of unclear output. The configure script works correctly, it just
prints jumbled output.
>
> A bit disturbing is this, finding yes and no for the same item, __int128
> (because libquadmath supports this data type?):
>
This is perfectly normal, __int128 is supported when building 64-bit
libraries and not when building 32-bit libraries.
Libquadmath provides routines for working with 128-bit floating-point
types, not integers.
> 5698:checking for ISO/IEC TR 24733 ... no
> 5699:checking for __int128... no
> 5700:checking for __float128... no
> 6269:checking for ISO/IEC TR 24733 ... no
> 6270:checking for __int128... yes
> 6271:checking for __float128... no
> 35967:checking for ISO/IEC TR 24733 ... no
> 35968:checking for __int128... no
> 35969:checking for __float128... no
> 36538:checking for ISO/IEC TR 24733 ... no
> 36539:checking for __int128... yes
> 36540:checking for __float128... no
> 66232:checking for ISO/IEC TR 24733 ... no
> 66233:checking for __int128... no
> 66234:checking for __float128... no
> 66803:checking for ISO/IEC TR 24733 ... no
> 66804:checking for __int128... yes
> 66805:checking for __float128... no
>
>
> (Disk space used after building: almost 5 GB.)
>
> --
> Greetings
>
> Pete
>
> A designer knows he has arrived at perfection not when there is no longer
> anything to add, but when there is no longer anything to take away.
> – Antoine de Saint-Exupéry
>
>
prev parent reply other threads:[~2022-12-01 8:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 10:19 Peter Dyballa
2022-11-25 11:22 ` Jonathan Wakely
2022-11-25 11:29 ` Jonathan Wakely
2022-11-25 11:39 ` Jonathan Wakely
2022-11-25 11:30 ` Peter Dyballa
2022-11-25 15:56 ` Segher Boessenkool
2022-11-25 16:50 ` Peter Dyballa
2022-11-25 19:43 ` Segher Boessenkool
2022-11-28 22:05 ` Peter Dyballa
2022-11-30 23:09 ` Peter Dyballa
2022-12-01 8:22 ` Jonathan Wakely [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH6eHdTS4U8_Pd+znHo6Su=Y4F3MMgsMe=96JZv+a+VPS41Kqw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=Peter_Dyballa@web.de \
--cc=gcc-help@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).