public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell" <carlos@systemhalted.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Mike Frysinger <vapier@gentoo.org>, libc-ports@sourceware.org
Subject: Re: [PATCH] hppa: use hidden_def with internal pthread funcs
Date: Tue, 20 Nov 2012 20:22:00 -0000	[thread overview]
Message-ID: <CAE2sS1hH_vF1PbS29Oh_stg3_S0Wr3vfUS9DpVOX=G1jqgLUXQ@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1211191423410.16273@digraph.polyomino.org.uk>

On Mon, Nov 19, 2012 at 9:32 AM, Joseph S. Myers
<joseph@codesourcery.com> wrote:
> On Mon, 19 Nov 2012, Carlos O'Donell wrote:
>
>> Hopefully things are a little better now for hppa, all I have left are
>> the _STACK_GROWS_UP patches for nptl/.
>
> I think points (b), (e), (g), (h), (k), (l), (m), (n), (o), (q), (r), (s),
> (t), (u), (v), (x) and (y) from my previous list
> <http://sourceware.org/ml/libc-ports/2012-06/msg00048.html> are still
> current, along with points not on that list:
>
>   (z) There is no c++-types.data for hppa.
>
>   (aa) The TLS configure checks should be removed from
>   sysdeps/hppa/configure.in, now the rule is that we assume a
>   recent-enough binutils and such checks are no longer needed for each
>   architecture and have been removed for other architectures.
>
>   (ab) __ASSUME_LWS_CAS (definition and uses) should be removed now
>   2.6.16 is the global minimum kernel version.
>
>   (ac) lll_futex_timed_wait_bitset should be defined for hppa.
>
> (Some of the bits/*.h files where my previous list notes the hppa versions
> are out of date should perhaps be reworked along the lines used for
> bits/fcntl.h to reduce duplication between architecture versions - but
> such a reworking wouldn't be appropriate during a release freeze, whereas
> straightforward updates of the hppa versions would be appropriate then.)

Thanks, that is correct and matches my list of remaining things that
need fixing.

My comment above is simply that with the patches for nptl
_STACK_GROWS_UP cases hppa will be able to compile and work
out-of-the-box without patches.

Cheers,
Carlos.

  reply	other threads:[~2012-11-20 20:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-18  9:04 Mike Frysinger
2012-11-19  5:46 ` Mike Frysinger
2012-11-19  5:48   ` Carlos O'Donell
2012-11-19  6:11     ` Mike Frysinger
2012-11-19  6:19       ` Carlos O'Donell
2012-11-19 14:33     ` Joseph S. Myers
2012-11-20 20:22       ` Carlos O'Donell [this message]
2012-11-20 23:42         ` Joseph S. Myers
2012-11-21  5:11           ` Carlos O'Donell
2012-11-19  5:46 ` 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='CAE2sS1hH_vF1PbS29Oh_stg3_S0Wr3vfUS9DpVOX=G1jqgLUXQ@mail.gmail.com' \
    --to=carlos@systemhalted.org \
    --cc=joseph@codesourcery.com \
    --cc=libc-ports@sourceware.org \
    --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).