From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "Michael Hope" <michael.hope@linaro.org>,
=?X-UNKNOWN?Q?Paulo_C=E9sar_Pereira_de_Andrade?=
<paulo.cesar.pereira.de.andrade@gmail.com>,
"Andrew Haley" <aph@redhat.com>,
cross-distro@lists.linaro.org,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"Richard Earnshaw" <rearnsha@arm.com>,
libc-ports@sourceware.org
Subject: Re: [PATCH] ARM: Use different linker path for hardfloat ABI
Date: Wed, 04 Apr 2012 09:16:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1204040913170.21733@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20120404065412.GJ16117@tyan-ft48-01.lab.bos.redhat.com>
On Wed, 4 Apr 2012, Jakub Jelinek wrote:
> If the agreement is that arm 32-bit softfp really needs to be installable
> alongside 32-bit hardfp (and alongside aarch64), then IMHO it should do it
> like all other multilib ports (x86_64/i?86/x32, s390/s390x, ppc/ppc64, the
> various MIPS variants) and what FSB says, e.g. use
> /lib/ld-linux.so.3 and */lib dirs for softfp,
> /libhf/ld-linux.so.3 and */libhf dirs for hardfp and
> /lib64/ld-linux.so.3 and */lib64 dirs for aarch64, have 32-bit
> arm-linux-gnueabi gcc configured for softfp/hardfp multilib with
> MULTILIB_OSDIRNAMES, etc., have it configured in glibc, and for those that
> choose the Debian layout instead, if it is added somehow configurable into
> upstream gcc/glibc of course handle it similarly there. I just wonder why
> that hasn't been done 10 years ago and only needs doing now (of course,
> aarch64 is going to be new, talking now about the 32-bit softfp vs. hardfp).
Exactly. The default should follow the existing practice for other
architectures.
> One needs to wonder also why arm hasn't switched to 128-bit long double when
> all other mainstream architectures did (I hope at least aarch64 will use it
> by default).
The AArch64 ABI (generic, not GNU/Linux, and draft, still subject to
incompatible change) is public and used 128-bit long double the last time
I checked.
My presumption is that there has been no demand for long double wider than
double among 32-bit ARM users.
--
Joseph S. Myers
joseph@codesourcery.com
next parent reply other threads:[~2012-04-04 9:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F7AC2E1.6010000@redhat.com>
[not found] ` <4F7AD4CA.8010000@arm.com>
[not found] ` <20120403110140.GG16117@tyan-ft48-01.lab.bos.redhat.com>
[not found] ` <4F7B20D2.8060608@arm.com>
[not found] ` <4F7B227F.7060905@redhat.com>
[not found] ` <CANLjY-mDvnn8NcVQfYoUUGZD72GbH7mgYjxWOGOzLMiUwNyp2Q@mail.gmail.com>
[not found] ` <20120403231133.GI16117@tyan-ft48-01.lab.bos.redhat.com>
[not found] ` <CANLjY-=dGK05kzvHVkuo3o7p_iE1cxfTi0f+t-RMmGW+37WSEg@mail.gmail.com>
[not found] ` <CAHAq8pE48=eY77adiKz3PEBapXwkPn6rjr3viMoUKpJq4x-G_A@mail.gmail.com>
[not found] ` <CANLjY-k-sC86gmaTH+h-5o4_D2MOnQHB4ihhDhoPt1HbUzJp9w@mail.gmail.com>
[not found] ` <20120404065412.GJ16117@tyan-ft48-01.lab.bos.redhat.com>
2012-04-04 9:16 ` Joseph S. Myers [this message]
[not found] <20120329193401.GA14860@dannf.org>
[not found] ` <4F75F2E2.3030909@arm.com>
[not found] ` <20120402210653.GC28152@dannf.org>
[not found] ` <CANLjY-nk7ML5QMBd0bKRJBA9stUOdvu1tWZqmFHxpRzObzFw1Q@mail.gmail.com>
2012-04-03 22:56 ` Joseph S. Myers
2012-04-04 2:40 ` Michael Hope
2012-04-04 9:06 ` Joseph S. Myers
2012-04-04 12:10 ` Dennis Gilmore
2012-04-05 13:30 ` Konstantinos Margaritis
2012-04-05 14:13 ` Niels de Vos
2012-04-05 15:08 ` Mike Frysinger
2012-04-05 15:24 ` Konstantinos Margaritis
2012-04-05 15:55 ` Mike Frysinger
2012-04-05 16:25 ` Konstantinos Margaritis
2012-04-10 4:10 ` Mike Frysinger
2012-04-05 16:16 ` Steve McIntyre
2012-04-05 17:36 ` Mike Frysinger
2012-04-04 23:33 ` Michael Hope
2012-04-05 0:07 ` Joseph S. Myers
2012-04-05 1:17 ` Michael Hope
2012-04-05 16:05 ` Steve McIntyre
2012-04-05 16:03 ` Steve McIntyre
2012-04-05 1:32 ` dann frazier
2012-04-05 14:57 ` Steve McIntyre
2012-04-10 20:31 ` Carlos O'Donell
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=Pine.LNX.4.64.1204040913170.21733@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=aph@redhat.com \
--cc=cross-distro@lists.linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=libc-ports@sourceware.org \
--cc=michael.hope@linaro.org \
--cc=paulo.cesar.pereira.de.andrade@gmail.com \
--cc=rearnsha@arm.com \
/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).