public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR 68192 Export AIX TLS symbols
Date: Tue, 03 Nov 2015 14:48:00 -0000	[thread overview]
Message-ID: <CAFiYyc0MUv4Rqa3nUoqr-8gishsWAXKfENZj4Ysqg-muvFCweg@mail.gmail.com> (raw)
In-Reply-To: <CAGWvnym=SO-wLDm+VKNPc2BJ20o8AOzpaRfkU1yFBsVLeQWhjA@mail.gmail.com>

On Tue, Nov 3, 2015 at 3:23 PM, David Edelsohn <dje.gcc@gmail.com> wrote:
> TLS symbols in AIX display a new, different symbol type in nm output.
> Libtool explicitly creates a list of exported symbols for shared
> libraries using nm and does not recognize the new TLS symbols, so
> those symbols are not exported.
>
> This is a regression for TLS support on AIX.
>
> This patch updates libtool.m4 in GCC and configure for libstdc++-v3,
> libgfortran, and libgomp.  I would like to apply the patch to GCC
> while I simultaneously work with the Libtool community to correct the
> bug upstream.  I also would like to backport this to GCC 5.2 and GCC
> 4.9.x.

What does this do to the set of exported symbols esp. on branches.
Does AIX have library versions?

> I have not been able to run the correct versions of autoconf to
> regenerate configure directly.  I either can edit the files directly
> or I would appreciate someone helping me to regenerate configure in
> all library directories.
>
> Bootstrapped on powerpc-ibm-aix7.1.0.0.
>
> * libtool.m4 (export_symbols_cmds) [AIX]: Add global TLS "L" symbols.
> * libstdc++-v3/configure: Regenerate.
> * libgfortran/configure: Regenerate.
> * libgomp/configure: Regenerate.
>
> Thanks, David

  reply	other threads:[~2015-11-03 14:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 14:23 David Edelsohn
2015-11-03 14:48 ` Richard Biener [this message]
2015-11-03 16:10   ` David Edelsohn
2015-11-24 16:28 ` Paolo Bonzini
2015-11-05 16:28 David Edelsohn
2015-11-05 16:34 ` Paolo Bonzini
2015-11-05 16:38   ` David Edelsohn
2015-11-05 17:13     ` Richard Biener
2015-11-05 17:20       ` David Edelsohn
2015-11-05 17:25     ` Paolo Bonzini
2015-11-06  3:54   ` Alexandre Oliva
2015-11-16  2:00     ` David Edelsohn
2015-11-16  8:22       ` Václav Haisman

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=CAFiYyc0MUv4Rqa3nUoqr-8gishsWAXKfENZj4Ysqg-muvFCweg@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.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).