public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Michael Hope <michael.hope@linaro.org>
Cc: Richard Earnshaw <rearnsha@arm.com>,
	       "Carlos O'Donell" <carlos@systemhalted.org>,
	       GCC Patches <gcc-patches@gcc.gnu.org>,
	       "cross-distro@lists.linaro.org"
	<cross-distro@lists.linaro.org>,
	       "libc-ports@sourceware.org" <libc-ports@sourceware.org>
Subject: Re: [PATCH v2] ARM: Use different linker path for hardfloat ABI
Date: Tue, 01 May 2012 03:46:00 -0000	[thread overview]
Message-ID: <4F9F5C16.8080202@redhat.com> (raw)
In-Reply-To: <CANLjY-kGg4T7WcZe6czWXzi-82Wg-DTKRDV-wMMb0mP8xaFEeA@mail.gmail.com>

On 04/30/2012 08:43 PM, Michael Hope wrote:
> On 1 May 2012 10:01, Jeff Law<law@redhat.com>  wrote:
>> On 04/30/2012 03:47 PM, Michael Hope wrote:
>>
>>>>>
>>>>> 2012-04-27  Michael Hope<michael.hope@linaro.org>
>>>>>
>>>>>        * config/arm/linux-eabi.h (GLIBC_DYNAMIC_LINKER): Pick the loader
>>>>>        using a spec rule.
>>>>>
>>>>
>>>> Michael,
>>>>
>>>> can you try this patch please.  It should make it possible to then
>>>> create linux-eabihf.h containing just
>>>>
>>>> #undef TARGET_DEFAULT_FLOAT_ABI
>>>> #define TARGET_DEFAULT_FLOAT_ABI ARM_FLOAT_ABI_HARD
>>>> #undef GLIBC_DYNAMIC_LINKER_DEFAULT
>>>> #define GLIBC_DYNAMIC_LINKER_DEFAULT GLIBC_DYNAMIC_LINKER_HARD_FLOAT
>>>>
>>>> Which is not quite as simple as leaving out the second re-define, but
>>>> pretty close.
>>>
>>>
>>> Hi Richard.  Your patch tests just fine.  I like it.  You could change
>>> the spec rule to the newer if-elseif-else form but that's a nit.
>>
>> So who owns creating the appropriate glibc patch now that we've got a good
>> gcc patch?
>
> Carlos is working on the GLIBC patch:
>   http://sourceware.org/ml/libc-ports/2012-04/msg00171.html
Ah, not on the main glibc list...  That's why I missed it.  Thanks.

jeff

  reply	other threads:[~2012-05-01  3:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-22 22:20 Michael Hope
2012-04-23 15:37 ` Richard Earnshaw
2012-04-23 21:37   ` Michael Hope
2012-04-24 13:32     ` Richard Earnshaw
2012-04-26 20:21     ` Carlos O'Donell
2012-04-26 23:27       ` Michael Hope
2012-04-30 15:24         ` Richard Earnshaw
2012-04-30 21:48           ` Michael Hope
2012-04-30 22:01             ` Jeff Law
2012-05-01  2:44               ` Michael Hope
2012-05-01  3:46                 ` Jeff Law [this message]
2012-05-01  8:52             ` Richard Earnshaw
2012-05-23  7:13               ` Andreas Jaeger
2012-05-23  7:56                 ` Richard Earnshaw
2012-05-23  8:01                   ` Andreas Jaeger
2012-05-23  8:18                     ` Richard Guenther
2012-05-23 14:15                       ` Mike Frysinger
2012-05-23 21:12                         ` Michael Hope
2012-05-24  4:08                           ` Mike Frysinger
2012-05-24  8:15                           ` Andrew Haley
2012-05-25  0:27                             ` Mike Frysinger
2012-05-25  8:24                               ` Andrew Haley
2012-05-24 17:08                       ` Jakub Jelinek
2012-04-23 19:58 ` 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=4F9F5C16.8080202@redhat.com \
    --to=law@redhat.com \
    --cc=carlos@systemhalted.org \
    --cc=cross-distro@lists.linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libc-ports@sourceware.org \
    --cc=michael.hope@linaro.org \
    --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).