graalvm-mobile

phronmophobic 2026-04-17T03:14:33.143809Z

https://github.com/phronmophobic/grease is back! Although, updating the docs is still a WIP so you may want to wait before checking it out.

🙌 5
rjsheperd 2026-04-17T04:12:48.326569Z

Nice! I was wondering how you feel about this fix for to be able to call certain ObjC functions without needing to add a stub to the to Bridge.h/m files: • Part 1: https://github.com/rjsheperd/libffi/commit/42929bea40f1599b964523a7e55303fb68040216 • Part 2: https://github.com/rjsheperd/clj-libffi/commit/8d7881eb85c2fe64156fbc00b494e0716867621a#diff-dd9b6f8ecac96ee4665e3ba64933aa2f1071312586520e587964fa0a85b38c6d

rjsheperd 2026-04-17T04:14:06.842979Z

Background: > When calling Objective-C methods via objc_msgSend on ARM64 iOS that return or accept Homogeneous Floating-point Aggregate (HFA) structs — e.g. =CLLocationCoordinate2D= ({double, double}, 16 bytes) as a return type, or MKCoordinateRegion ({double×4}, 32 bytes) as a by-value argument — libffi selects the wrong ARM64 calling convention, producing incorrect values or crashes.

phronmophobic 2026-04-17T04:17:39.036119Z

I'm not sure I understand the problem

phronmophobic 2026-04-17T04:18:13.774569Z

What makes you think libffi is selecting the wrong calling convention?