So where is 7u14 beast and why doesn't it become publicly visible? After all it's a 'feature-release' so there should be no reason to hide it behind the fences, right?
Regards, Volker On Fri, Apr 12, 2013 at 5:30 PM, Alejandro E Murillo <[email protected]> wrote: > Requesting approval to integrate hs24-b40 into jdk7u14-b21. > > A webrev is available at: > > http://cr.openjdk.java.net/~amurillo/7u14/hs24-b40-jdk7u14-b21.webrev/ > > Pre-integration testing is in progress; the integration will proceed > only after SQE has analyzed the results and approved. > > The fixes in the proposed integration are below. All have undergone > nightly testing and are already in a jdk8 repository. > > 7107135: Stack guard pages are no more protected after loading a shared > library with executable stack > 7178741: SA: jstack -m produce UnalignedAddressException in output (Linux) > 8004640: C2 assert failure in memnode.cpp: NULL+offs not RAW address > 8006753: fix failed for JDK-8002415 White box testing API for HotSpot > 8007701: Hotspot trace allocation events > 8008081: Print outs do not have matching arguments > 8008737: The trace event vm/gc/heap/summary is missing for CMS > 8008917: CMS: Concurrent mode failure tracing event > 8008920: Tracing events for heap statistics > 8009032: Implement evacuation info event > 8009460: C2compiler crash in machnode::in_regmask(unsigned int) > 8010294: Refactor HeapInspection to make it more reusable > 8010651: create.bat still builds the kernel > 8010916: Add tenuring threshold to young garbage collection events > 8011021: new hotspot build - hs24-b39 > 8011400: missing define OPENJDK for windows builds > 8011583: new hotspot build - hs24-b40 > 8011699: CMS: assert(_shared_gc_info.id() != SharedGCInfo::UNSET_GCID) > failed: GC not started? > > -- > Alejandro >
