From: Wei-min Pan <weimin.pan@oracle.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PING 6][PATCH PR gdb/18071] TLS variables can't be resolved on aarch64-linux-gnu
Date: Wed, 14 Mar 2018 21:34:00 -0000 [thread overview]
Message-ID: <6a937e34-cc76-bd8e-2d4e-b989b5ddf119@oracle.com> (raw)
In-Reply-To: <8d2efd960d637a9adc8888a39e54a9c1@polymtl.ca>
Hi Simon,
Thanks for taking this up. Yao did take a look at the patch late last
year but didn't have time to finish it up.
Please let me know if you have comments/questions.
Weimin
On 3/14/2018 2:06 PM, Simon Marchi wrote:
> Hi Weimin,
>
> This is just to tell you that I started looking into this, since Yao
> will likely not have the time to do it (though I don't mind if he
> does!). But it might take a bit of time since I don't know much about
> the particular case of TLS on aarch64, so I'll need to ramp up on it.
>
> Simon
prev parent reply other threads:[~2018-03-14 21:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1509636764-46111-1-git-send-email-weimin.pan@oracle.com>
2017-11-16 1:53 ` [PING][PATCH " Wei-min Pan
2018-01-16 17:12 ` Yao Qi
2018-01-17 1:05 ` Weimin Pan
2018-01-17 8:57 ` Yao Qi
2018-01-18 0:18 ` Wei-min Pan
[not found] ` <515b875f-8240-b7e0-f5cc-4a26efb64b89@oracle.com>
2018-01-12 23:59 ` [PING 2][PATCH " Weimin Pan
[not found] ` <64a638db-13e1-e692-f775-9afc19677a2a@oracle.com>
2018-01-24 1:11 ` [PING 3][PATCH " Weimin Pan
2018-02-06 1:21 ` [PING 4][PATCH " Weimin Pan
2018-03-06 1:21 ` [PING 5][PATCH " Weimin Pan
2018-03-13 18:56 ` [PING 6][PATCH " Weimin Pan
2018-03-14 21:06 ` Simon Marchi
2018-03-14 21:34 ` Wei-min Pan [this message]
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=6a937e34-cc76-bd8e-2d4e-b989b5ddf119@oracle.com \
--to=weimin.pan@oracle.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).