-
Notifications
You must be signed in to change notification settings - Fork 258
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 silently ignores garbage target versions #1728
Comments
Also see internal issue, http://b/236753843 (Platform build system passes codename for clang -target, which expects an integer). |
good task for intern so i'm claiming it. |
see also internal issue http://b/315788463 where this is still silently breaking things internally 1.5 years later... |
Even options like |
Now I just detect the version after |
yeah sure. |
@ZijunZhaoCCK fixed the "invalid version" parts in llvm/llvm-project#75373. We will pull this into the next release. There is follow-up to detect invalid "environments" ( |
@pirama-arumuga-nainar since it was merged last week, you mean the next-next release, right? r28? Or is that going to be cherry-picked into the r27 toolchain? |
We can cherry-pick to the r27 toolchain. |
Description
Invalid android versions are silently ignored by clang.
In the second case,
android/api-level.h
(which will be included transitively by any file that includes any libc header) will set__ANDROID_API__
to__ANDROID_API_FUTURE__
(AKA 10000), but won't set__ANDROID_MIN_SDK_VERSION__
at all.Upstream bug
No response
Commit to cherry-pick
No response
Affected versions
r24, r25, Canary
Canary version
No response
Host OS
Linux, Mac, Windows
Host OS version
all
Affected ABIs
armeabi-v7a, arm64-v8a, x86, x86_64
The text was updated successfully, but these errors were encountered: