Pls review (S) 7117389: Add a framework for vendor-specific command line switch extensions to Hotspot
Charles K Pepperdine
kirk at kodewerk.com
Sat Dec 3 05:01:25 PST 2011
Does this imply that if I wanted to add a command line switch for my commercial product that was "embedded" into the JVM I would have to do this in a special build? I'm trying to sort out how this would work?
On Dec 2, 2011, at 4:54 PM, Paul Hohensee wrote:
> Webrev here:
> This webrev defines and uses, but does not implement, a switch extension interface.
> I've added a new file, globals_ext.hpp, that contains hooks for vendor-specific additions
> to the set of Hotspot command line switches and added their use to globals.hpp,
> globals.cpp and globals_extension.hpp. I chose "_ext" as a generic suffix for files
> containing extension hooks. In effect, such files are interface definitions. A vendor
> supplies a file, perhaps of the same name in another source base (as can be seen in
> the Hotspot makefiles), that implements the extension hooks.
More information about the hotspot-dev