[llvm-branch-commits] [compiler-rt] release/22.x: [compiler-rt] fix __sanitizer::struct_sock_fprog_sz availability (#183411) (PR #193288)
thesamesam wrote: I don't insist if you feel uncomfortable. We can backport it downstream. https://github.com/llvm/llvm-project/pull/193288 ___ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
[llvm-branch-commits] [compiler-rt] release/22.x: [compiler-rt] fix __sanitizer::struct_sock_fprog_sz availability (#183411) (PR #193288)
https://github.com/thesamesam closed https://github.com/llvm/llvm-project/pull/193288 ___ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
[llvm-branch-commits] [compiler-rt] release/22.x: [compiler-rt] fix __sanitizer::struct_sock_fprog_sz availability (#183411) (PR #193288)
dyung wrote: @thesamesam thanks for the explanation. That being said, it appears the breakage was introduced all the way back in the LLVM 20 time period and only fully fixed 3 weeks ago which seemingly indicates that this feature is not used widely, or some work-around did exist? While it might be nice to get it in, I'm inclined to defer the fix to LLVM 23 which arrives in just a few months for these reasons. Is there a critical scenario that fixing this would unblock that cannot be worked around some other way? https://github.com/llvm/llvm-project/pull/193288 ___ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
[llvm-branch-commits] [compiler-rt] release/22.x: [compiler-rt] fix __sanitizer::struct_sock_fprog_sz availability (#183411) (PR #193288)
dyung wrote: This seems to me more of adding a feature than really a critical bug fix that we would want for inclusion in the release branch at this time. Can you help me to understand what adding this to the release branch would fix? https://github.com/llvm/llvm-project/pull/193288 ___ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
[llvm-branch-commits] [compiler-rt] release/22.x: [compiler-rt] fix __sanitizer::struct_sock_fprog_sz availability (#183411) (PR #193288)
https://github.com/vitalybuka approved this pull request. https://github.com/llvm/llvm-project/pull/193288 ___ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
[llvm-branch-commits] [compiler-rt] release/22.x: [compiler-rt] fix __sanitizer::struct_sock_fprog_sz availability (#183411) (PR #193288)
https://github.com/devnexen approved this pull request. https://github.com/llvm/llvm-project/pull/193288 ___ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
[llvm-branch-commits] [compiler-rt] release/22.x: [compiler-rt] fix __sanitizer::struct_sock_fprog_sz availability (#183411) (PR #193288)
github-actions[bot] wrote: ⚠️ We detected that you are using a GitHub private e-mail address to contribute to the repo. Please turn off [Keep my email addresses private](https://github.com/settings/emails) setting in your account. See [LLVM Developer Policy](https://llvm.org/docs/DeveloperPolicy.html#email-addresses) and [LLVM Discourse](https://discourse.llvm.org/t/hidden-emails-on-github-should-we-do-something-about-it) for more information. https://github.com/llvm/llvm-project/pull/193288 ___ llvm-branch-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
