From: Andreas Enge <andreas@enge.fr>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 47349@debbugs.gnu.org, Carl Dong <contact@carldong.me>
Subject: [bug#47349] [PATCH] gnu: cross-base: Relax check for powerpc64le
Date: Fri, 26 Mar 2021 11:31:16 +0100 [thread overview]
Message-ID: <YF239JK0GpUb1z0k@jurong> (raw)
In-Reply-To: <871rc2bfb9.fsf@gmail.com>
Hello Chris,
I have no idea about cross compilers, but it would certainly be nice if
the final gcc supported long doubles.
As a check, you can have a look at the log file for building gmp,
obtained with "guix build --log-file gmp". If you grep for "long double",
it should contain a line
checking for long double... yes
Hm, just "having" long double is maybe not all we want.
From the gcc documentation at https://gcc.gnu.org/install/configure.html:
--with-long-double-128
Specify if long double type should be 128-bit by default on selected GNU/Linux architectures. If using --without-long-double-128, long double will be by default 64-bit, the same as double type. When neither of these configure options are used, the default will be 128-bit long double when built against GNU C Library 2.4 and later, 64-bit long double otherwise.
Of course we would like long double to have 128 bits, since otherwise there
is no difference with double. And at least with the current gcc and a glibc
from 2006 or later, the flag should not be neeed.
On my x86_64 machine, sizeof(long double) is 16 bytes with gcc@10, 5 or 7.
Could you try to compile and run the trivial program
#include <stdio.h>
void main () {
printf ("long double %i\n", sizeof (long double));
}
and see what it outputs on powerpc?
Well, while --with-long-double-128 should not be needed since it should be
the default, you may as well add it to the flags, since it is the desired
behaviour.
Andreas
next prev parent reply other threads:[~2021-03-26 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 16:02 [bug#47349] [PATCH] gnu: cross-base: Relax check for powerpc64le Carl Dong
2021-03-25 16:09 ` Léo Le Bouter via Guix-patches via
2021-03-26 6:27 ` Chris Marusich
2021-03-26 10:31 ` Andreas Enge [this message]
2021-03-26 14:33 ` Léo Le Bouter via Guix-patches via
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=YF239JK0GpUb1z0k@jurong \
--to=andreas@enge.fr \
--cc=47349@debbugs.gnu.org \
--cc=cmmarusich@gmail.com \
--cc=contact@carldong.me \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.