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
Hello, I have encountered a problem compiling a library under Windows using Clang, during compilation the compiler crashes, but in this particular case it is a problem on the llvm backend side, I created an issue there https://github.com/llvm/llvm-project/issues/119255 and the guys have already found the problem, it is caused by the x86-winehstate pass, that is, it is incorrect code generation by the compiler itself and there are no errors in your library. But this error is indirectly related to the use of exceptions (try-catch) and their implementation in windows. This also applies not only to the cppcoro library but also to the concurencpp library, I wrote an issue there too.
I would like to ask you, if it is not difficult for you, please implement the library interfaces without using try-catch and throw, just as it is implemented in the standard library, where we have function overloads for using them both with try-catch blocks and for getting the error code by passing a pointer to std::error_code to the function.
Not only would this solve the Clang problem, but it could also help the library be used in embedded systems where there is no exception catching mechanism, if you avoided using try-catch and throw in private library implementations.
The text was updated successfully, but these errors were encountered:
Hello, I have encountered a problem compiling a library under Windows using Clang, during compilation the compiler crashes, but in this particular case it is a problem on the llvm backend side, I created an issue there https://github.com/llvm/llvm-project/issues/119255 and the guys have already found the problem, it is caused by the
x86-winehstate
pass, that is, it is incorrect code generation by the compiler itself and there are no errors in your library. But this error is indirectly related to the use of exceptions (try-catch) and their implementation in windows. This also applies not only to thecppcoro
library but also to theconcurencpp
library, I wrote an issue there too.I would like to ask you, if it is not difficult for you, please implement the library interfaces without using try-catch and throw, just as it is implemented in the standard library, where we have function overloads for using them both with try-catch blocks and for getting the error code by passing a pointer to std::error_code to the function.
Not only would this solve the Clang problem, but it could also help the library be used in embedded systems where there is no exception catching mechanism, if you avoided using try-catch and throw in private library implementations.
The text was updated successfully, but these errors were encountered: