You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be a mis-compilation on Linux x86_64 with CFAttributedString that the rebranch uncovered. @etcwilde and I managed to reduce it down to a single file, but have not reduced it further. Unfortunately, it involves LICM, LoadStoreHoisting, and inlining potentially. In order to unblock the rebranch, this file might need to be optimized at -O0 on linux.
The following are the known failing tests associated with this issue:
Unfortunately, it is very difficult to debug. lldb consistently crashes when trying to execute any of these tests and gdb is unable to show a valid stack trace. Additionally, these only happen on optimized builds, so that throws more fun into the mix.
The text was updated successfully, but these errors were encountered:
@etcwilde was able to validate an approach that I had in mind. The issue is in the C/C++ side and we can test with the upstream clang. Using that, we were able to validate that CF built with upstream clang does fix the issue, which means that this has been fixed upstream. We can bisect to find the fix.
Alright, I think I've narrowed the fix down to llvm commit 909cba969981032c5740774ca84a34b7f76b909b. Time to cherry-pick and see if things keep exploding.
Additional Detail from JIRA
md5: c31f76109ebd2918e05a0e3882c68286
Issue Description:
There seems to be a mis-compilation on Linux x86_64 with
CFAttributedString
that the rebranch uncovered. @etcwilde and I managed to reduce it down to a single file, but have not reduced it further. Unfortunately, it involves LICM, LoadStoreHoisting, and inlining potentially. In order to unblock the rebranch, this file might need to be optimized at-O0
on linux.The following are the known failing tests associated with this issue:
Unfortunately, it is very difficult to debug. lldb consistently crashes when trying to execute any of these tests and gdb is unable to show a valid stack trace. Additionally, these only happen on optimized builds, so that throws more fun into the mix.
The text was updated successfully, but these errors were encountered: