RFR: 8199220: Zero build broken after 8195103 and 8191102 (was RFR: 8199220: Zero build broken) (original) (raw)
Edward Nevill edward.nevill at gmail.com
Mon Mar 12 19:27:10 UTC 2018
- Previous message: RFR: 8199220: Zero build broken after 8195103 and 8191102 (was RFR: 8199220: Zero build broken)
- Next message: RFR: 8199220: Zero build broken after 8195103 and 8191102 (was RFR: 8199220: Zero build broken)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, 2018-03-12 at 13:57 +1000, David Holmes wrote:
Hi Ed,
Once we're certain this addresses all the issues it was intended to address (ref Thomas's email) you should generate a final changeset with the exact changes (ie Coleen's comment) and the final set of reviewers, and post the link. I'll take that re-run through our internal tests and then push.
Hi David,
Thanks for your patience. New webrev here
http://cr.openjdk.java.net/~enevill/8199220/webrev.03
I have updated the webrev to build the debug version of zero which has been broken since Nov 20, 2017 by change 8189871.
https://bugs.openjdk.java.net/browse/JDK-8189871
This caused the error
/home/ed/openjdk/hs/src/hotspot/share/utilities/debug.hpp:184:29: error: incomplete type ‘STATIC_ASSERT_FAILURE’ used in nested name specifier
I have also addressed Coleen's comment.
Build tested zero release/debug and server release/debug,
Thanks for you help, Ed.
- Previous message: RFR: 8199220: Zero build broken after 8195103 and 8191102 (was RFR: 8199220: Zero build broken)
- Next message: RFR: 8199220: Zero build broken after 8195103 and 8191102 (was RFR: 8199220: Zero build broken)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]