This was mentioned in #939 but unfortunately did not get enough attraction.
Quoting @atsushieno:
Well, Android x86 target is real on emulators especially with HAXM enabled. It is something significant.
Without this target, we are forced to use real devices or emulators based on arm (not being updated anymore: latest one was still Android 7) which is 10x slower than x86-based emulators according to Google. That could be inconvenient during development.
Also, iOS targets do have ios_x64 which is specifically for emulators (I think), so I really couldn't understand why proper Android emulators are not supported.
x86 specifically or x86_64 ? In which case, see https://github.com/JetBrains/kotlin/pull/2538
Maybe android_x86 is also needed, since only x86 is in the "recommended" system images:

But there are x86_64 images too, so there could be some people using them.
x86 is very important for emulator, and especially for cases when you use it on CI
@olonho This PR covers only Android x86_64, are there any plans to support Android x86?
It's not hard to do, with toolchain architecture changed in this PR, but someone got to convince me that it is indeed needed.
@olonho
This statistics doesn't include any non-certificated devices (ones without Google Play Services) such as TV boxes, GPS trackers, navigators, car head units, players, and many other devices that use Android as OS but do not provide access to Google Play
For image references please see the above reply (11 days ago). That's from AVD manager.
Most helpful comment
Maybe
android_x86is also needed, since only x86 is in the "recommended" system images:But there are x86_64 images too, so there could be some people using them.