We should migrate SWT GTK3 and GTK4 for use FFM. I already prototyped that and have a running Eclipse IDE based on https://github.com/vogella/eclipse.platform.swt/tree/ffm-migration.
Not yet covered: GTK4, WebKit, GLX and the AWT bridge on Linux, Win32 and Cocoa.
Also not yet done: C.java and Callback.java to FFM in the product build as they live in shared folders that the win32 and cocoa builds also compile, and those have no FFM version. That's why the product build still loads the JNI libraries.
Good news is, IDE starts without any failures and according to the SWT tests, our vogella SWT harness and our vogella Eclipse harness the IDE is pixel identical.
Performance with FFM is currently worse compared to JNI, we are currently investigating.
We should migrate SWT GTK3 and GTK4 for use FFM. I already prototyped that and have a running Eclipse IDE based on https://github.com/vogella/eclipse.platform.swt/tree/ffm-migration.
Not yet covered: GTK4, WebKit, GLX and the AWT bridge on Linux, Win32 and Cocoa.
Also not yet done: C.java and Callback.java to FFM in the product build as they live in shared folders that the win32 and cocoa builds also compile, and those have no FFM version. That's why the product build still loads the JNI libraries.
Good news is, IDE starts without any failures and according to the SWT tests, our vogella SWT harness and our vogella Eclipse harness the IDE is pixel identical.
Performance with FFM is currently worse compared to JNI, we are currently investigating.