Remove Legacy ABI Compatibility

[hmelder]

We are carrying a lot of dead-weight just by supporting the old GCC ABI which probably no one uses in combination with libobjc2.

There are still lot more ugly hacks which can be removed.

[davidchisnall]

Isn’t there more to be deleted from the upgrade logic?

[hmelder]

Isn’t there more to be deleted from the upgrade logic?

Yeah but I was not sure how much to delete. Do we want to leave the gsv1 upgrade logic in place or remove it as well?

[hmelder]

And this would fall under OLDABI_COMPAT right?

[davidchisnall]

Isn’t there more to be deleted from the upgrade logic?

Yeah but I was not sure how much to delete. Do we want to leave the gsv1 upgrade logic in place or remove it as well?

I'm not sure. We currently don't support the new ABI on Mach-O in clang and it's quite useful to be able to run tests on macOS so that we can compare their behaviour against the Apple runtime. I've not tried WebAssembly, but it probably also needs some custom work.

The main reason I'd drop the GCC ABI is that anyone using GCC should probably use their runtime. Ideally we'd get every target supported by the v1 GNUstep ABI onto v2 and then drop v1 as well.

[hmelder]

We currently don't support the new ABI on Mach-O in clang

I did not know that we support v1 on Macho-O. It would be very interesting to support v2 as well just for benchmarking purposes.

[hmelder]

I'll remove the GCC upgrade logic then.

[hmelder]

Google recently updated the clang prebuilds for the Android SDK. The fast path test now executes and fails instead of being skipped.