[Bug libgcc/109054] _Unwind_GetLanguageSpecificData should have protected visibility

2023-03-07 Thread woodard at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109054 Ben Woodard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libgcc/109054] _Unwind_GetLanguageSpecificData should have protected visibility

2023-03-07 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109054 --- Comment #4 from Jakub Jelinek --- As I tried to explain, because libgcc_s and libstdc++ are different libraries, there is nothing that can be done on the GCC side. You can avoid libunwind (which is a good idea, it is a terrible library from

[Bug libgcc/109054] _Unwind_GetLanguageSpecificData should have protected visibility

2023-03-07 Thread woodard at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109054 --- Comment #3 from Ben Woodard --- Actually what we were hoping to achieve was not to substitute another version of _Unwind_GetLanguageSpecificData for the one that is in libgcc_s.so but rather to make it so that that another implementation of

[Bug libgcc/109054] _Unwind_GetLanguageSpecificData should have protected visibility

2023-03-07 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109054 Jakub Jelinek changed: What|Removed |Added CC||fw at gcc dot gnu.org --- Comment #2

[Bug libgcc/109054] _Unwind_GetLanguageSpecificData should have protected visibility

2023-03-07 Thread jakub at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109054 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment