public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: Paolo Bonzini <bonzini@gnu.org>,
	Alexandre Oliva <aoliva@redhat.com>,
		GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR 68192 Export AIX TLS symbols
Date: Thu, 05 Nov 2015 17:20:00 -0000	[thread overview]
Message-ID: <CAGWvnykZ8Ps_MCrGFuRaFccf5ACGyY7NKVpwg0YdTyXED-9Kmg@mail.gmail.com> (raw)
In-Reply-To: <D2FD3DA4-DF44-4362-AF69-0C39C670F4B5@gmail.com>

Hi, Richi

You mentioned GCC 5.3 release around the time of stage 1 ending in the
GCC 5 status report:

https://gcc.gnu.org/ml/gcc/2015-07/msg00197.html

If the timeframe is later, we have more time to address the AIX libtool problem.

Thanks, David

On Thu, Nov 5, 2015 at 9:13 AM, Richard Biener
<richard.guenther@gmail.com> wrote:
> On November 5, 2015 5:38:45 PM GMT+01:00, David Edelsohn <dje.gcc@gmail.com> wrote:
>>On Thu, Nov 5, 2015 at 8:34 AM, Paolo Bonzini <bonzini@gnu.org> wrote:
>>>
>>>
>>> On 05/11/2015 17:28, David Edelsohn wrote:
>>>> [Explicitly copying build maintainers.]
>>>>
>>>> Paolo and Alexandre,
>>>>
>>>> Could you review and help with this patch?
>>>>
>>>> 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.
>>>
>>> I think it's okay to wait for the patch to be upstream.
>>>
>>> I can help committing the patch once it is.
>>
>>Paolo,
>>
>>The patch MUST go into GCC 5.3 release, which Richi has announced that
>>he wants to release around the beginning of Stage 3.  The patch should
>>not go into GCC 5 branch without going into trunk.  This patch cannot
>>wait unless you want to block GCC 5.3.
>
> I don't remember announcing this timeframe but I won't be able to dedicate the required resources until the end of November.
>
> Richard.
>
>>Thanks, David
>
>

  reply	other threads:[~2015-11-05 17:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2015-11-03 14:23 David Edelsohn
2015-11-03 14:48 ` Richard Biener
2015-11-03 16:10   ` David Edelsohn
2015-11-24 16:28 ` Paolo Bonzini

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=CAGWvnykZ8Ps_MCrGFuRaFccf5ACGyY7NKVpwg0YdTyXED-9Kmg@mail.gmail.com \
    --to=dje.gcc@gmail.com \
    --cc=aoliva@redhat.com \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.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).