RFR: 8217445: [JVMCI] incorrect management of JVMCI compilation failure reason string
tobias.hartmann at oracle.com
Tue Jan 22 08:00:21 UTC 2019
looks good to me too.
On 21.01.19 13:57, Doug Simon wrote:
> The CompileTask::_failure_reason field assumes it is only ever assigned a compile-time constant string value (i.e. never needs to be freed). This is not the case when the value is derived from a JVMCI exception message. This patch adds support for managing a C heap allocated value in this field.
More information about the hotspot-compiler-dev