RFR 8201799: Build failures after JDK-8195099 (Concurrent safe-memory-reclamation mechanism) (original) (raw)
Thomas Schatzl thomas.schatzl at oracle.com
Wed Apr 18 12:39:46 UTC 2018
- Previous message: RFR 8201799: Build failures after JDK-8195099 (Concurrent safe-memory-reclamation mechanism)
- Next message: RFR 8201799: Build failures after JDK-8195099 (Concurrent safe-memory-reclamation mechanism)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
On Wed, 2018-04-18 at 13:50 +0200, Aleksey Shipilev wrote:
Bug: https://bugs.openjdk.java.net/browse/JDK-8201799
Fix: diff -r bfba4712d4ff src/hotspot/share/utilities/globalCounter.inline.hpp --- a/src/hotspot/share/utilities/globalCounter.inline.hpp Wed Apr 18 11:36:48 2018 +0200 +++ b/src/hotspot/share/utilities/globalCounter.inline.hpp Wed Apr 18 13:50:34 2018 +0200 @@ -27,6 +27,7 @@ #include "runtime/orderAccess.inline.hpp" #include "runtime/thread.hpp"
Agree with David that this line should be removed before pushing.
+#include "runtime/thread.inline.hpp" #include "utilities/globalCounter.hpp"
inline void GlobalCounter::criticalsectionbegin(Thread *thread) { Testing: failing aarch64 build
Seems good to go.
Thomas
- Previous message: RFR 8201799: Build failures after JDK-8195099 (Concurrent safe-memory-reclamation mechanism)
- Next message: RFR 8201799: Build failures after JDK-8195099 (Concurrent safe-memory-reclamation mechanism)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]