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
ICE on Android/ARM, related to recent LTO change in master #1860
Comments
What if you comment-out setting the "use-soft-float" attribute? It wasn't clear to me how to set it for the SoftFP ABI type. |
Yeah, commenting that line out fixes it and gets all stdlib tests passing again. |
Thanks for testing, so now I have to figure out how to set things correctly for ARM. Perhaps an extra setting is needed. I'll have a look at what clang generates for the triples you specified. |
I think I've fixed it in #1863 . Sorry for breaking things, it's an underdocumented part of LLVM :( |
Fixed by #1863. |
Follow guides at https://wiki.dlang.org/Build_D_for_Android ldc-build-runtime --reset --ninja --targetPreset=Android-arm failed
Any advice? Thanks |
see #2406 |
I've been building natively on Android/ARM with the latest llvm 3.9.0 release, I ran into this ICE when building druntime synced against latest master:
I bisected and found that the issue is #1811, reverting that patch has master passing all stdlib and dmd tests again (there's an unrelated failure in the dmd testsuite because of the recently added test16225, which adds the
-m64
flag and doesn't work because I don't compile in the ARM64 backend on ARM32).This is the command run on my Android tablet, same as on any other platform:
You should be able to reproduce by using an ldc compiled against llvm with an ARM backend and adding the flag
-mtriple=armv7-none-linux-android
or-mtriple=armv7-unknown-linux-gnueabi
. If not, let me know.The text was updated successfully, but these errors were encountered: