From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Mike Frysinger <vapier@gentoo.org>,
Harold Grovesteen <h.grovsteen@tx.rr.com>
Subject: Re: [Fwd: Re: [PATCH 1 of 3] arch: s390 and 390x glibc patch]
Date: Sun, 15 Nov 2009 00:37:00 -0000 [thread overview]
Message-ID: <200911150136.44241.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <200911141128.27056.vapier@gentoo.org>
On Saturday 14 November 2009 17:28:26 Mike Frysinger wrote:
> > > > Mike Frysinger wrote:
> > > > >under Gentoo, a bunch of cache vars
> > > > >are forced just for the headers step as there is no compiler to test.
> > > > > those include mlong double tests.
> > > > > libc_cv_mlong_double_128=yes
> > > > > libc_cv_mlong_double_128ibm=yes
> these are settings that should always be there and the user shouldnt be forced
> to configure themselves. it also isnt specific to s390 ... it comes up with
> ppc targets too.
> for the headers step, it's safe to export these all the time for all targets.
> we've been doing this in gentoo for quite a long time now.
You mean unconditionally? On my x86_64 machine, debian lenny:
- in 64-bit mode: sizeof( long double ) = 16 bytes = 128 bits
- in 32-bit mode: sizeof( long double ) = 12 bytes = 96 bits
So, does it really makes sense to _unconditionnally_ set long-double-128?
The gcc man page says that on x86 (32-bit) the ABI specifies a size of
96 bits for long double.
Also, what does long-double-128ibm means?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
`------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2009-11-15 0:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 22:56 Harold Grovesteen
2009-11-11 23:18 ` Mike Frysinger
[not found] ` <4AFB4AC8.2000103@tx.rr.com>
2009-11-14 15:21 ` Mike Frysinger
2009-11-14 15:57 ` Yann E. MORIN
2009-11-14 16:26 ` Mike Frysinger
2009-11-14 20:52 ` Harold Grovesteen
2009-11-15 1:12 ` Mike Frysinger
2009-11-15 0:37 ` Yann E. MORIN [this message]
2009-11-15 1:12 ` Mike Frysinger
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=200911150136.44241.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=crossgcc@sourceware.org \
--cc=h.grovsteen@tx.rr.com \
--cc=vapier@gentoo.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).