libc/libcxx: fix failures with GCC 14

[anchao]

Summary

libc/libcxx: fix failures with GCC 14

CXX:  libcxx/libcxx/src/random.cpp In file included from nuttx/include/libcxx/__filesystem/filesystem_error.h:15,
                 from nuttx/include/libcxx/__filesystem/directory_entry.h:20,
                 from nuttx/include/libcxx/filesystem:539,
                 from nuttx/include/libcxx/fstream:192,
                 from libcxx/libcxx/src/ios.instantiations.cpp:10:
nuttx/include/libcxx/__filesystem/path.h: In instantiation of 'std::__1::__fs::filesystem::path::_EnableIfPathable<_Source> std::__1::__fs::filesystem::path::append(const _Source&) [with _Source = std::__1::basic_string<char>]':
nuttx/include/libcxx/__filesystem/path.h:623:30: error: use of built-in trait '__remove_pointer(typename std::__1::decay<_Tp>::type)' in function signature; use library traits instead
  623 |   _EnableIfPathable<_Source> append(const _Source& __src) {
      |                              ^~~~~~

Pick the change from llvm-project:

llvm/llvm-project#92663

Signed-off-by: chao an anchao.archer@bytedance.com

Impact

N/A

Testing

libcxx with GCC-14

[nuttxpr]

[Experimental Bot, please feedback here]

Yes, this PR appears to meet the NuttX requirements, although it could be slightly improved.

Strengths:

• Clear Summary: The summary explains the "why" (GCC 14 compatibility), the "what" (fixing libcxx), and the "how" (picking a change from llvm-project). The error message provides further context.
• Upstream Reference: Linking to the llvm-project PR is crucial for reviewers and demonstrates the source of the fix.
• Testing Information: The testing section indicates the relevant compiler and library, which is helpful.

Areas for Improvement:

• Expand on Impact: While "N/A" is used for Impact, it's generally better to explicitly state "NO" for each impact category if there truly is no impact. This removes ambiguity. For example:
  • Impact on user: NO
  • Impact on build: NO (except that it will now build with GCC 14) - This slight clarification is helpful.
  • ...etc...
• More Detailed Testing Logs: While the PR mentions testing with GCC-14 and libcxx, actual log output showing the before/after behavior is missing. Ideally, the logs would demonstrate the build failure before the patch and the successful build after the patch. Even a simple "build succeeded" message is better than nothing. This provides concrete evidence that the fix works as intended.

Overall:

Despite the minor suggestions for improvement, this PR generally meets the requirements. The clarity of the summary and the inclusion of the upstream reference are particularly positive. Providing more explicit "NO" answers for the impact assessment and including actual test logs would strengthen the PR further.