[OpenJDK 2D-Dev] RFR(XS): 7196866: CTW fails on Solaris (original) (raw)
Phil Race philip.race at oracle.com
Thu May 16 23:24:58 UTC 2013
- Previous message: [OpenJDK 2D-Dev] RFR(XS): 7196866: CTW fails on Solaris
- Next message: [OpenJDK 2D-Dev] [8] request for review: 8000936 Enable Java2D D3D pipeline on newer Intel chipsets : Intel HD and later
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I agree, that I don't think we need to go so far as that. I've concluded that the original proposed fix appears harmless and is very probably OK and the low incidence of such CTW issues over the years is surprising but reassuring. I've been waiting (all afternoon!) for my fastdebug (*) build to complete so I can see for sure how we enter the code that crashes in case there is anything that we are missing that goes beyond what is needed by CTW. But you can go ahead with your fix. Anything else I find we can deal with separately.
(*) fastdebug clearly refers solely to its runtime performance characterisrics, not its build speed.
-phil.
On 5/16/2013 3:48 PM, John Rose wrote:
On May 16, 2013, at 3:28 PM, Morris Meyer <morris.meyer at oracle.com_ _<mailto:morris.meyer at oracle.com>> wrote:
Perhaps I should throw an ExceptionInInitializerError w a CompileTheWorld message? That goes farther beyond native code hardening than I was thinking. If I were Phil I'd be uncomfortable with that, because it appears to create more of a contract than simply "don't crash". — John
- Previous message: [OpenJDK 2D-Dev] RFR(XS): 7196866: CTW fails on Solaris
- Next message: [OpenJDK 2D-Dev] [8] request for review: 8000936 Enable Java2D D3D pipeline on newer Intel chipsets : Intel HD and later
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]