JavaMemoryModel: Volatile isn't used in most code

• Next message: Bill Pugh: "JavaMemoryModel: quick opcodes unsafe under weak memory models"
• Previous message: Paul Haahr: "Re: JavaMemoryModel: final isn't used much in the JDK, even when it could"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

I checked, and all of the benchmarks I tried, I only
found a handfull of fields marked volatile:

com/adobe/acrobat/file/URLByteStream.closed
com/adobe/acrobat/gui/IronCityPrint$PrinterDialog$PrinterList.loadComplete
com/adobe/acrobat/sidecar/ImageGraphics$ImageProxy.imageDone
com/adobe/pe/awt/VPaintingCanvasDrawThread.stop
com/adobe/util/ImageMonitor.imageDone
com/adobe/util/ImageMonitor.height
com/adobe/util/ImageMonitor.width

../benchmarks/visaj.jar
ice/htmlbrowser/AppletStatus.loaded
ice/htmlbrowser/AppletStatus.inited
ice/htmlbrowser/AppletStatus.running
ice/htmlbrowser/AppletStatus.destroyed
ice/htmlbrowser/AppletStatus.disposed
ice/htmlbrowser/BoxImage.imageError
ice/htmlbrowser/BoxImage.iwidth
ice/htmlbrowser/BoxImage.iheight
ice/htmlbrowser/VisDocument.start_flag

../benchmarks/tools.jar
sun/tools/agent/Agent.debuggerTerminating
-------------------------------
This is the JavaMemoryModel mailing list, managed by Majordomo 1.94.4.

To send a message to the list, email JavaMemoryModel@cs.umd.edu
To send a request to the list, email majordomo@cs.umd.edu and put
your request in the body of the message (use the request "help" for help).
For more information, visit http://www.cs.umd.edu/~pugh/java/memoryModel

• Next message: Bill Pugh: "JavaMemoryModel: quick opcodes unsafe under weak memory models"
• Previous message: Paul Haahr: "Re: JavaMemoryModel: final isn't used much in the JDK, even when it could"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

This archive was generated by hypermail 2b29 : Thu Oct 13 2005 - 07:00:17 EDT