OopStorage provides `operator new` taking a MEMFLAGS argument, so the allocation of the storage object can be specified according to the owning subsystem. This goes along with the MEMFLAGS constructor argument.
Now that we have CHeapObjBase we can make OopStorage derived from it to provide the `operator new` with MEMFLAGS argument.
That derivation will also provide an appropriate `operator delete`; the `operator delete` with MEMFLAGS argument currently defined by OopStorage is a mistake.
Now that we have CHeapObjBase we can make OopStorage derived from it to provide the `operator new` with MEMFLAGS argument.
That derivation will also provide an appropriate `operator delete`; the `operator delete` with MEMFLAGS argument currently defined by OopStorage is a mistake.
- relates to
-
JDK-8294308 Allow dynamically choosing the MEMFLAGS of a type without ResourceObj
-
- Resolved
-
