Java Memory Model mailing list archive
By Subject
2503 messages sorted by:
[ author ]
[ date ]
[ thread ]
About this archive
Mail actions: [ mail a new topic ]
Starting: Thu Jun 24 1999 - 11:18:00 EDT
Ending: Wed Aug 24 2005 - 14:49:54 EDT
- "Design Pattern: Singleton in C#" is dangerously flawed
- "Double-Checked Locking is Broken"
- Are the volatile semantics strong enough?
- Are this$x fields final?
- Audience of Java memory model mailing list
- BOUNCE javamemorymodel@cs.umd.edu: Non-member submission from [karthikeyan pck <kars_77@yahoo.com>]
- Data races should not be the buffer overflow of the 21st century
- Dealing with scopes in real-time Java
- Double null check sync problem fix.
- Double-check and Symantec JIT
- feedback: SC- Memory Model for Java
- Finializers again (this is important)
- Getting the ball rolling
- Getting the ball rolling...
- Important typo fix in unified model description: U6 is not allowed
- Introduction, class author responsibilities (was: JavaMemoryModel: Idiom for safe, unsynchronized reads)
- Java Memory Model and exceptions ?
- JavaMemoryModel: "Causality"
- JavaMemoryModel: "synchronizes with"
- JavaMemoryModel: (Non)-Usefulness of data races on NON_VOLATILE fields
- JavaMemoryModel: (Proposal) Semantics must satisfy Linking Monotonicity.
- JavaMemoryModel: 30 day review period for JSR-133
- JavaMemoryModel: 8/3 Bay area trip report
- JavaMemoryModel: [ANN] Paper on Java Memory Models
- JavaMemoryModel: [ANN]: JmmSolve 0.1.2: generative implementation of CCMs
- JavaMemoryModel: [ANN]: JmmSolve 0.1: generative implementation of CCMs
- JavaMemoryModel: [Figure fix]: Should we prohibit all causal loops?
- JavaMemoryModel: [Fwd: double check article: what if constructor throws exception]
- JavaMemoryModel: A Better Way?
- JavaMemoryModel: A constraint-based approach for memory model specification and analysis
- JavaMemoryModel: A couple of things...
- JavaMemoryModel: A different slant with reference leakage
- JavaMemoryModel: A major problem with CnC
- JavaMemoryModel: A memory model for the masses
- JavaMemoryModel: a naive proposal
- JavaMemoryModel: A new box for the Java Memory model
- JavaMemoryModel: A new JMM specification framework
- JavaMemoryModel: A new memory model for Java
- JavaMemoryModel: A paper on JMM
- JavaMemoryModel: A performance argument against acquire/relea se ordering, a call for a quantitative approach, and a naive proposal
- JavaMemoryModel: A performance argument against acquire/release ordering, a call for a quantitative approach, and a naive proposal
- JavaMemoryModel: A problematical case f or finalizers)
- JavaMemoryModel: A problematical case for finalizers
- JavaMemoryModel: A simplified version of my model
- JavaMemoryModel: A two-phase approach to resolve causal loops
- JavaMemoryModel: Access to final members by super through overloaded methods
- JavaMemoryModel: acquire & releases on volatile variables
- JavaMemoryModel: Actions and GUIDs
- JavaMemoryModel: Agreement to disagree: where things stand
- JavaMemoryModel: allowed semantics question
- JavaMemoryModel: Alpha Memory model doesn't support fast
- JavaMemoryModel: Alpha Memory model doesn't support fast & safe OO languages
- JavaMemoryModel: alpha version of JavaMemoryModel-digest now available
- JavaMemoryModel: An incomplete case for multiple models
- JavaMemoryModel: An incorrectly synchronized case
- JavaMemoryModel: an operational model?
- JavaMemoryModel: Announce: Bug pattern detector for Java
- JavaMemoryModel: Another approach
- JavaMemoryModel: Another attempt at formalizing finalization; need particular attention from parallel GC people
- JavaMemoryModel: Another important finalizer question
- JavaMemoryModel: Another Java threading issue (finalization)
- JavaMemoryModel: Another litmus test for strong vs. weak volatiles
- JavaMemoryModel: Another place where the default value isn't acceptable
- JavaMemoryModel: another question on volatile
- JavaMemoryModel: Another software-only solution
- JavaMemoryModel: Any more objective technical concerns for SC-?
- JavaMemoryModel: Are 'final' fields cause the GC to be more efficient?
- JavaMemoryModel: Are correctly synchronized code fragment executions SC?
- JavaMemoryModel: Are the volatile semantics strong enough?
- JavaMemoryModel: Are this$x fields final?
- JavaMemoryModel: Argument for a strong memory model
- JavaMemoryModel: Array
- JavaMemoryModel: Atomic classes (was: New function needed in java.lang.Thread?)
- JavaMemoryModel: AtomicXArrays
- JavaMemoryModel: Behavior in test case 7 not allowed by SC-3
- JavaMemoryModel: Bill's model and LC
- JavaMemoryModel: BOF at OOPSLA
- JavaMemoryModel: Bug fixed in test case 6; A and B should initially be 0
- JavaMemoryModel: Bugs in Tiger beta 1
- JavaMemoryModel: Bypassing class initialization checks with quick opcodes
- JavaMemoryModel: C# Memory Model?
- JavaMemoryModel: Call for Papers: Concurrency and Synchronization in Java Programs Workshop
- JavaMemoryModel: Call for Papers: Java Concurrency Workshop
- JavaMemoryModel: Can final fields change?
- JavaMemoryModel: causal warps
- JavaMemoryModel: Causality Test 16
- JavaMemoryModel: Causality vs. CnC causality
- JavaMemoryModel: Changed my mind on final fields
- JavaMemoryModel: Choice of formalism for the JSR-133 memory model
- JavaMemoryModel: circular reasoning in compilers & memory models...
- JavaMemoryModel: Clarification of final field safe contexts
- JavaMemoryModel: Clarification: Acquire/Release Semantics On Volatile Read/Write Is New?
- JavaMemoryModel: class author responsibilities JavaMemoryModel: Idiom for safe, unsynchronized reads)
- JavaMemoryModel: class initialization (was: Idiom for safe, unsynchronized reads)
- JavaMemoryModel: Class initialization safety is hard
- JavaMemoryModel: Class Loaders and Garbage Collection
- JavaMemoryModel: CnC in SC- framework
- JavaMemoryModel: Code in the JDK that fails under current memory model
- JavaMemoryModel: Code that sleeps and expects to see changes
- JavaMemoryModel: Coming down to the end on JSR-133
- JavaMemoryModel: Commentary on a new memory model for Java
- JavaMemoryModel: Comments on JSR-133 document (Feb 2, 2004)
- JavaMemoryModel: Comments on Sarita's example for our model, and on Sarita's model
- JavaMemoryModel: Comments on Sarita's suggested changes
- JavaMemoryModel: Communicating Process Architectures ...
- JavaMemoryModel: Community Review Draft updated
- JavaMemoryModel: Concurrency Utilities BOF at JavaOne
- JavaMemoryModel: Confirmation that we are using strong volatile semantics
- JavaMemoryModel: Cookbook: barriers
- JavaMemoryModel: Corner cases for final fields
- JavaMemoryModel: correct string issue summary?
- JavaMemoryModel: correct synchronization
- JavaMemoryModel: Correction to litmus test V4
- JavaMemoryModel: Correspondence with Sandhya on Treadmarks
- JavaMemoryModel: cost of initialization-safety on an Alpha SMP
- JavaMemoryModel: Cost of marking things volatile
- JavaMemoryModel: Cost of memory barriers, and the difficulty of removing them
- JavaMemoryModel: CSJP deadine extended
- JavaMemoryModel: Current compliance with volatile?
- JavaMemoryModel: Current stage of proposed Java memory model?
- JavaMemoryModel: Current status of proposed memory model
- JavaMemoryModel: Data races should not be the buffer overflow of the 21st century
- JavaMemoryModel: Dead email addresses
- JavaMemoryModel: Dealing with scopes in real-time Java
- JavaMemoryModel: Definition of volatile revisited
- JavaMemoryModel: Definitive citation for double-check idiom
- JavaMemoryModel: deleting dead volatile ref's
- JavaMemoryModel: Deliberate undersynchronization
- JavaMemoryModel: Dependences: [Fwd from Cliff]
- JavaMemoryModel: Dependences: a concrete example
- JavaMemoryModel: Deserializing transient final fields
- JavaMemoryModel: Deserializing transient final fields (was: Will String be secure?)
- JavaMemoryModel: Disallowing badly synchronized programs
- JavaMemoryModel: Do any JVM's move memory accesses across native calls?
- JavaMemoryModel: Do getfield/putfield correspond to use/assign or load/store?
- JavaMemoryModel: Do we need to allow this behavior?
- JavaMemoryModel: Do we need to bother with corner cases for final fields
- JavaMemoryModel: Does everyone agree that volatile variables should be SC
- JavaMemoryModel: Double checked locking in C#
- JavaMemoryModel: Double-check and Symantec JIT
- JavaMemoryModel: Double-Checked Locking is Broken
- JavaMemoryModel: Double-Checked-Locking - revisited
- JavaMemoryModel: Draft JMM Synopsis
- JavaMemoryModel: Draft JSR-133 Cookbook for compiler writers
- JavaMemoryModel: Draft of Complete Memory Model now available!
- JavaMemoryModel: Draft of JavaOne talk
- JavaMemoryModel: Draft of JSR-133 Community Review document; submit to JCP tomorrow
- JavaMemoryModel: Draft version of JSR-133 public review document
- JavaMemoryModel: Dropping coherence is more complicated than we thought
- JavaMemoryModel: Dropping coherence is more complicated thanwe thought
- JavaMemoryModel: ECMA CLI/C# spec
- JavaMemoryModel: Efficient class initialization is _very_ hard
- JavaMemoryModel: Efficient implementation of strong class initialization safety
- JavaMemoryModel: Email from Josh on extending thread functionality
- JavaMemoryModel: Empirical benefits of strong volatile rules
- JavaMemoryModel: Empirical data on cost of barriers in Cilk
- JavaMemoryModel: Employing copy-on-write & avoiding double-check idiom
- JavaMemoryModel: Empty synchronized blocks are not useless (? )
- JavaMemoryModel: Empty synchronized blocks are not useless (?)
- JavaMemoryModel: Examples similar to tests 5 and 10
- JavaMemoryModel: Executable specifications
- JavaMemoryModel: Executions I find profoundly troubling
- JavaMemoryModel: Executors, Thread Pools and Isolation
- JavaMemoryModel: Experimental Memory Model Without Forbidden Executions
- JavaMemoryModel: Explaination of litmus test V4
- JavaMemoryModel: Fairness Guarantees in the Memory Model?
- JavaMemoryModel: Final and Volatile array classes
- JavaMemoryModel: Final clarification on volatiles
- JavaMemoryModel: Final fields and deserialization
- JavaMemoryModel: final fields, again
- JavaMemoryModel: final isn't used much in the JDK, even when it could
- JavaMemoryModel: Final Means Different Things To VM and Java Language. Does That Impact JITs?
- JavaMemoryModel: Final Semantics?
- JavaMemoryModel: final, pseudo-final and write protected fields
- JavaMemoryModel: final, pseudo-final and write protectedfields
- JavaMemoryModel: finalization
- JavaMemoryModel: Finalization idioms
- JavaMemoryModel: finalization review
- JavaMemoryModel: Finalization, again
- JavaMemoryModel: finalize semantics
- JavaMemoryModel: Finalizer question
- JavaMemoryModel: Finalizers
- JavaMemoryModel: Finalizers must be run in a finalizer thread
- JavaMemoryModel: Finializers again (this is important)
- JavaMemoryModel: First reason on broken Double Check Locking
- JavaMemoryModel: Forwarded email from Ras Bodik on speculative writes
- JavaMemoryModel: From "Elements of Java Style"....
- JavaMemoryModel: From "Elements of Java Style".... :-(
- JavaMemoryModel: fusing synch blocks
- JavaMemoryModel: Fwd: Performing speculative writes ahead of loops that may not terminate
- JavaMemoryModel: FWD: Question regarding nested synchronized blocks
- JavaMemoryModel: General rules
- JavaMemoryModel: Goals for the memory model and alternatives
- JavaMemoryModel: Good news on IA-64
- JavaMemoryModel: Guaranteed semantics for Thread.yield()
- JavaMemoryModel: Happy birthday JMM mailing list
- JavaMemoryModel: Here we go...
- JavaMemoryModel: High-level necessary and sufficient requirements for a Java memory model
- JavaMemoryModel: high-level summary of our approach and differences from Sarita
- JavaMemoryModel: Hoist by my own petard; the real difference between 5 & 6
- JavaMemoryModel: Holub's Rules to Live By
- JavaMemoryModel: How about "Synchronizes to" and "Synchronize s from"
- JavaMemoryModel: How about "Synchronizes to" and "Synchronizes from"
- JavaMemoryModel: How bad are incorrectly synchronized program s?
- JavaMemoryModel: How bad are incorrectly synchronized programs?
- JavaMemoryModel: How figure 2 example is forbidden by the original JMM
- JavaMemoryModel: How relaxed should our memory model be?
- JavaMemoryModel: how to insert a memory barrier when using java.nio shared memory?
- JavaMemoryModel: I take this back - Causality vs. CnC causality
- JavaMemoryModel: Idiom for safe, unsynchronized reads
- JavaMemoryModel: If your posts don't show up
- JavaMemoryModel: Immutable objects which aren't immutable
- JavaMemoryModel: Immutablity and Final Fields
- JavaMemoryModel: Implementing atomic object creation on Alphas may be cheap
- JavaMemoryModel: Implementing KeepAlive
- JavaMemoryModel: Implications of SC-: we need your feedback
- JavaMemoryModel: Importance of volatile performance
- JavaMemoryModel: Important typo fix in unified model description: U6 is not allowed
- JavaMemoryModel: IMPORTANT: New Unified JMM formalism, $100 reward for any flaws
- JavaMemoryModel: Indirect loads and processor consistency
- JavaMemoryModel: Information about IA-64 memory operations
- JavaMemoryModel: init methods
- JavaMemoryModel: init methods [From Josh]
- JavaMemoryModel: Intentional data race in String.hashCode()
- JavaMemoryModel: Interaction between the memory model and exc eptions
- JavaMemoryModel: Interaction between the memory model and exc eptions, Tread.stop()
- JavaMemoryModel: Interaction between the memory model and exc eptions, Tread.stop()]
- JavaMemoryModel: Interaction between the memory model and exceptions
- JavaMemoryModel: Interaction between the memory model and exceptions]
- JavaMemoryModel: Interactions with the environment and non-determinism
- JavaMemoryModel: Introductions
- JavaMemoryModel: Introductions...
- JavaMemoryModel: Is "memory coherence" necessary in the new JMM?
- JavaMemoryModel: Is reordering of dependent reads on Alpha actually possible?
- JavaMemoryModel: Isolation properties in the JMM
- JavaMemoryModel: Issue with final fields
- JavaMemoryModel: Issues in the real-time java spec
- JavaMemoryModel: Java and architectures w/ aggressive reordering
- JavaMemoryModel: Java Class initialization can deadlock?
- JavaMemoryModel: Java memory model paper at ICSE 2002
- JavaMemoryModel: Java memory model workshop at OPPSLA
- JavaMemoryModel: Java's insecure parallelism
- JavaMemoryModel: Javadoc terminology for synchronization
- JavaMemoryModel: javaMemoryModel: volatile, final, etc.
- JavaMemoryModel: JavaOne
- JavaMemoryModel: JavaOne 2004 Presentation
- JavaMemoryModel: Javasoft bug reports
- JavaMemoryM