Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Clang build error on Windows #93

Open
artemsazonov86 opened this issue Dec 10, 2024 · 0 comments
Open

[BUG] Clang build error on Windows #93

artemsazonov86 opened this issue Dec 10, 2024 · 0 comments

Comments

@artemsazonov86
Copy link

artemsazonov86 commented Dec 10, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant