RFR: 7903933: Move sharable items from different generations to a common file [v4]

[Maurizio Cimadamore]

On Thu, 27 Mar 2025 14:49:36 GMT, Jorn Vernee <jvernee at openjdk.org> wrote:

> > this means that there will always be at least two header classes generated foo_f and foo_h$0, where foo_h extends foo_h$0 and all the shared symbols are in foo_h$0.
> 
> Should we just give the base header a common name then, so that if you generate multiple times, you get sharing automatically? Maybe it could be named something like `Builtins`.

Yes, see

> This is similar, in spirit, to what you have here, but with the advantage that there's only one generation scheme, not two -- e.g. the superclass with the shared symbol is always there -- only sometimes it can have a different name (because the user said so). Whether we want that default superclass name to be foo_h$0, or maybe something more explicit like foo_h_shared, I'm open to suggestions.

-------------

PR Comment: https://git.openjdk.org/jextract/pull/278#issuecomment-2758398120