修复POSIX线程本地存储寻找posix线程句柄时的逻辑错误

[atwwww]

拉取/合并请求描述：(PR description)

[

为什么提交这份PR (why to submit this PR)

修复POSIX线程本地存储寻找posix线程句柄时的逻辑错误
修复GCC emutls C++11 thread_local关键字的逻辑正确性

你的解决方案是什么 (what is your solution)

修改pthread_getspecific、pthread_setspecific函数中通过rt_thread_self()获取POSIX线程句柄的方式
ptd = (_pthread_data_t *)rt_thread_self()->user_data;
修改为：
ptd = (_pthread_data_t *)rt_thread_self()->pthread_data;

rt_thread_self()->user_data是RT-Thread原生private user_data
rt_thread_self()->pthread_data->tls是POSIX层TLS

请提供验证的bsp和config (provide the config and bsp)

• BSP:
  bsp\stm32\stm32f407-atk-explorer

• .config:
  #define RT_USING_CPLUSPLUS
  #define RT_USING_CPLUSPLUS11

• action:
  编译通过：
  

修改前：
对于POSIX-TLS：
(ptd != NULL) assertion failed at function:pthread_setspecific, line number:61
对于C++11 thread_local：
初始值由GCC传入，emutls为每个线程赋值。但获取TLS时出现问题
(ptd != NULL) assertion failed at function:pthread_getspecific, line number:36

修改后：
能够正常使用：

]

当前拉取/合并请求的状态 Intent for your PR

必须选择一项 Choose one (Mandatory):

• 本拉取/合并请求是一个草稿版本 This PR is for a code-review and is intended to get feedback
• 本拉取/合并请求是一个成熟版本 This PR is mature, and ready to be integrated into the repo

代码质量 Code Quality：

我在这个拉取/合并请求中已经考虑了 As part of this pull request, I've considered the following:

• 已经仔细查看过代码改动的对比 Already check the difference between PR and old code
• 代码风格正确，包括缩进空格，命名及其他风格 Style guide is adhered to, including spacing, naming and other styles
• 没有垃圾代码，代码尽量精简，不包含#if 0代码，不包含已经被注释了的代码 All redundant code is removed and cleaned up
• 所有变更均有原因及合理的，并且不会影响到其他软件组件代码或BSP All modifications are justified and not affect other components or BSP
• 对难懂代码均提供对应的注释 I've commented appropriately where code is tricky
• 代码是高质量的 Code in this PR is of high quality
• 已经使用formatting 等源码格式化工具确保格式符合RT-Thread代码规范 This PR complies with RT-Thread code specification

[polarvid]

Relates to #6229

[atwwww]

Relates to #6229

Thank you for your reply.

Shall I close this?

#6229 seems had been merged into master branch:

But it seems no changes in current master branch?

[polarvid]

Relates to #6229

Thank you for your reply.

Shall I close this?

#6229 seems had been merged into master branch:

But it seems no changes in current master branch?

这份提交中修复的问题应该是 #6229 中忽略的部分。

[atwwww]

Relates to #6229

Thank you for your reply.
Shall I close this?
#6229 seems had been merged into master branch:
But it seems no changes in current master branch?

这份提交中修复的问题应该是 #6229 中忽略的部分。

看起来是这样的。
感谢回复。