Consider giving names to split functions

[yotann]

Because split functions have no name, the globalopt pass (included in opt -O1) deletes them. If we give all the split functions a standardized name (like f) this won't be a problem. However, any name we choose could potentially conflict with other names used by the program.

Another option: store split functions without a name, but give users the option to add a name when retrieving a function from the BCDB.

[regehr]

optionally naming would be excellent for my use case!

[regehr]

I wrote a silly pass to name these functions, so feel free to deprioritize this if it doesn't help anyone but me