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
Compilation failure on 32-bit and 64-bit arm platforms with a recent clang #7787
Comments
The issue you link to is about the compiler and processor, not about the OS. We recently fixed an issue where clang was picking up the wrong assembly code on some arm CPUs, can you please try the latest If not, can you please let us know how to reproduce the problem: exact compiler command line, preferably one that doesn't require a “fancy” development kit and works on Linux. We do not plan to add integration to the operating systems, i.e. platform support, TLS stack integration, build script, etc. |
Oh, it failed with a different error? So is the Is that in the same configuration with the same compiler? The errors in your latest links seem to be specific to a compile-time configuration (and perhaps 32-bit/64-bit), whereas the errors in your original report were about a combination of compiler and target CPU. |
Is because they test in github action following their test suite using your development branch and im testing using a simple executable. |
I have installed everything locally, including the mbedtls development branch and now get these errors: iOS:
watchOS:
tvOS:
macOS:
Android:
macOS without leetal cmake (https://github.com/leetal/ios-cmake):
If you want that i test any branch with custom code to check if was solved, only post here that i can test now locally fast. |
The interesting one for me is The code is
and so because |
@paulocoutinhox Note that all the warnings in our latest post are harmless (the compiler's picky but the code's ok). If you disable |
We've just merged a fix so that there are no compiler warnings with clang 15 in the default configuration with I'm reopening this issue because there are apparently more warnings in the LMS code which we haven't addressed. |
Hi, That warning was fixed, now have other:
|
Oh, so that one is apparently a 64-bit platform, since line 82 in Or maybe we're not doing the right thing for It would help if the issue was focused on a single platform, rather than mixing many issues into one. |
Hi, About arm64_32 of apple watch:
I will add here some warnings using current version in development branch. tvOS:
macOS:
watchOS error:
|
@paulocoutinhox please could you confirm if #7808 fixes this. Do you have any suggestions as to what the command line should look like in order to get clang to build ILP32 in order to test this? Thanks |
Hi @daverodgman I post the error on your PR. |
Hi @daverodgman, The watchOS bug was fixed. But the iOS, macOS and tvOS problems with the warnings not. I need create a new issue? |
The conversion warnings are captured in #7813 , so I'm closing this issue. The conversion warnings doesn't seem to be a simple fix, so I recommend disabling Thanks for your help in resolving the ILP32 issue. |
Hi,
Can you add support for watchOS, tvOS and iOS?
Reference:
yasio/yasio#416 (comment)
Thanks.
The text was updated successfully, but these errors were encountered: