no-assume-compiled is undocumented and probably broken, but some software,
particularly Eclipse, relies on it. When indirect-dispatch works well enough for
Eclipse we should rip out no-assume-compiled.
I wonder if we should instead keep the no-assume-compiled
command-line processing, and reuse it to decide when
to generate more tightly bound code and when to generate
The internal "no-assume-compiled ABI" should definitely be
I was thinking the same thing. We could perhaps think of a better name for it
This is fairly low priority because it doesn't really affect anything.
However, removing no-assume-compiled could cause considerable lossage.
For the time being, we could simply remove the command line option.
Closing as won't fix as the Java front-end has been removed from the trunk.