public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Chris Metcalf <cmetcalf@tilera.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: <libc-ports@sourceware.org>, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] tile: improve detection for missing -mcmodel=large support
Date: Fri, 24 May 2013 02:05:00 -0000	[thread overview]
Message-ID: <519ECAF3.1040700@tilera.com> (raw)
In-Reply-To: <519E9585.1090904@redhat.com>

(Adding David explicitly to Cc.)

On 5/23/2013 6:17 PM, Carlos O'Donell wrote:
> On 05/23/2013 03:20 PM, Chris Metcalf wrote:
>> The existing test avoided passing -mcmodel=large if the compiler didn't
>> support it.  However, we need to test not just the compiler support, but
>> also the toolchain (as and ld) support, so make the test more complete.
>> In addition, we have to avoid using the hwN_plt() assembly operators if
>> that support is missing, so guard the uses with #ifdef NO_PLT_PCREL.
>>
>> This allows us to properly build glibc with the current community
>> binutils, which doesn't yet have the PC-relative PLT operator support.
>> The -mcmodel=large support is in gcc 4.8, but the toolchain support
>> won't be present in the community until binutils 2.24.
>> ---
>> This change should also be applied on the 2.17 release branch for
>> when we release a 2.17.1.
> No, just backport it immediately after checkin to master. The 2.17
> branch *is* 2.17.1 in development and when we get enough changes in
> that branch we cut it and make a 2.17.1 release.
>
> You need release manager ACK though, which is David Miller. We normally
> handle backports via bugzilla bugs with keyword glibc_2.17, but it
> can be less formal if you just CC David and ask for ACK.

David, is it OK if I backport this to the 2.17 branch after I commit?  Do you want a BZ# to track it?

-- 
Chris Metcalf, Tilera Corp.
http://www.tilera.com

  reply	other threads:[~2013-05-24  2:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 19:25 Chris Metcalf
2013-05-23 22:17 ` Carlos O'Donell
2013-05-24  2:05   ` Chris Metcalf [this message]
2013-05-28 18:37     ` Chris Metcalf
2013-06-06 20:10       ` Chris Metcalf
2013-06-06 21:36         ` David Miller
2013-06-09 15:22           ` Chris Metcalf

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=519ECAF3.1040700@tilera.com \
    --to=cmetcalf@tilera.com \
    --cc=carlos@redhat.com \
    --cc=davem@davemloft.net \
    --cc=libc-ports@sourceware.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).