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
- JavaMemoryModel: javaworld on double-check
- JavaMemoryModel: JLS3 contains glitch concerning volatiles?
- JavaMemoryModel: JMM and caches.
- JavaMemoryModel: JMM Beta version
- JavaMemoryModel: JMM discussions moving to https://javamemorymodel.dev.java.net/
- JavaMemoryModel: JMM Final draft Freeze Complete today!
- JavaMemoryModel: JMM not moving to https://javamemorymodel.dev.java.net/
- JavaMemoryModel: JMM on clusters
- JavaMemoryModel: JMM problems with latch or copy-on-write?
- JavaMemoryModel: JMM, escape analysis, lock elision
- JavaMemoryModel: JMM: Fig. 24
- JavaMemoryModel: Josh's finalizer guardian??
- JavaMemoryModel: JSR 133 Status report
- JavaMemoryModel: JSR 166 (Concurrency utilities)
- JavaMemoryModel: JSR-133 going twice...
- JavaMemoryModel: JSR-133 is in public review
- JavaMemoryModel: JSR-133 proceeding to public final draft without JLS chapter
- JavaMemoryModel: JSR-133 proposed final draft
- JavaMemoryModel: JSR-133 status and plans
- JavaMemoryModel: jsr-133 status report
- JavaMemoryModel: JSR-133 status, schedule and process
- JavaMemoryModel: JSR-133 Voting Results
- JavaMemoryModel: JSR133 - Java Memory Model
- JavaMemoryModel: JSR133 para 12.2 wording.
- JavaMemoryModel: JSR133-related division of labor between javac and JVM
- JavaMemoryModel: Language semantics cannot depend upon optimization flags
- JavaMemoryModel: LC model and LC cache protocol
- JavaMemoryModel: Legal implementations
- JavaMemoryModel: Legality of native code changing final field s
- JavaMemoryModel: Legality of native code changing final fields
- JavaMemoryModel: Let them write race-free code (was: The prop erty of "race-free implies SC")
- JavaMemoryModel: Let them write race-free code (was: The property of "race-free implies SC")
- JavaMemoryModel: Loops, programming languages, and weak fairness
- JavaMemoryModel: Loosing the global ordering
- JavaMemoryModel: Lowering the stakes in this discussion
- JavaMemoryModel: Lunch/dinner get together at OOPSLA?
- JavaMemoryModel: Mailing list was down over the weekend
- JavaMemoryModel: Major yuck! GET/PUTSTATIC prohibits reordering
- JavaMemoryModel: Major yuck! GET/PUTSTATIC prohibitsreordering
- JavaMemoryModel: Mechanization of core memory model
- JavaMemoryModel: Memory model and finalize methods
- JavaMemoryModel: Memory model BOF at OOPSLA
- JavaMemoryModel: Memory Model JSR status report
- JavaMemoryModel: Memory Model updates in the CLR
- JavaMemoryModel: memoryModel BOF at OOPSLA?
- JavaMemoryModel: Minor issue on hb edges and interrupts
- JavaMemoryModel: missing ingredient of volatile semantic
- JavaMemoryModel: Model Checking the CRF JMM
- JavaMemoryModel: more double-checked fun
- JavaMemoryModel: more double-checked fun [Fwd from Josh]
- JavaMemoryModel: More from Cliff on exceptions
- JavaMemoryModel: More info on C#
- JavaMemoryModel: More on C#
- JavaMemoryModel: More ordering constraints does not imply mor e reliable software
- JavaMemoryModel: More ordering constraints does not imply more reliable software
- JavaMemoryModel: More Specification
- JavaMemoryModel: More synchronization statistics
- JavaMemoryModel: Most (all?) JVM's incorrectly handle volatile reads-after-writes
- JavaMemoryModel: Most (all?) JVM's incorrectly handlevolatile reads-after-writes
- JavaMemoryModel: Motivation and Semantics for Immutable objects
- JavaMemoryModel: Motivation and Semantics for Immutable objects]
- JavaMemoryModel: Motivation and Semantics for Immutableobjects
- JavaMemoryModel: Motivation/intuition for new model
- JavaMemoryModel: movement into synchronized blocks
- JavaMemoryModel: Moving memory operations across external actions
- JavaMemoryModel: Mutual exclusion effect of locks
- JavaMemoryModel: Mutually exclusive goals for Java memory model
- JavaMemoryModel: my 2 cents (not that its worth that much)
- JavaMemoryModel: My approach
- JavaMemoryModel: My final summary of strong vs. weak volatile semantics
- JavaMemoryModel: Native code and the changing of final fields
- JavaMemoryModel: Native code destroys code analysis?
- JavaMemoryModel: Native methods and Final fields
- JavaMemoryModel: Need to submit postings from same address as you are subscribed to
- JavaMemoryModel: New approach to defining the Java Memory Model
- JavaMemoryModel: New Causality Test
- JavaMemoryModel: New description/presentation of semantics of final fields
- JavaMemoryModel: New document
- JavaMemoryModel: New function needed in java.lang.Thread?
- JavaMemoryModel: New one page version of Manson/Pugh core model
- JavaMemoryModel: new papers - FYI
- JavaMemoryModel: New Semantics for Final Fields
- JavaMemoryModel: New test case?
- JavaMemoryModel: New Unified JMM Description
- JavaMemoryModel: New Updated Documents
- JavaMemoryModel: Newbie Question
- JavaMemoryModel: Newer revisions
- JavaMemoryModel: No "Spooky errors at a distance"
- JavaMemoryModel: No decision on lost notifications
- JavaMemoryModel: Non SC behaviour using volatiles.
- JavaMemoryModel: Non-atomic volatile writes
- JavaMemoryModel: Non-Atomic Volatiles
- JavaMemoryModel: non-finals with synchronized getters
- JavaMemoryModel: Object.hashCode() and System.identityHashCode()
- JavaMemoryModel: october JMM spec seems to break java's threading model
- JavaMemoryModel: Ok, last thing Monday, rather than first thing
- JavaMemoryModel: OK, time to get moving again
- JavaMemoryModel: On which JDK 1.4 VMs is "volatile access" already compliant with the proposed JDK 1.5 JMM?
- JavaMemoryModel: Oops... Forgot non-atomic volatile writes
- JavaMemoryModel: OOPSLA BOF scheduling
- JavaMemoryModel: OOPSLA poster submission on weak memory models - chance to review
- JavaMemoryModel: OOPSLA workshop
- JavaMemoryModel: OOPSLA workshop call for participation
- JavaMemoryModel: OOPSLA Workshop?
- JavaMemoryModel: operation reorderings
- JavaMemoryModel: operation reorderings [Corrected]
- JavaMemoryModel: Ordering of volatile and monitor actions
- JavaMemoryModel: OT: Semantics for yield and sleep
- JavaMemoryModel: Our latest trial balloon
- JavaMemoryModel: Out-of-scope variables and finalization
- JavaMemoryModel: paper announcement
- JavaMemoryModel: Paper by Arvind on memory models that may be of interest
- JavaMemoryModel: PC language alert: catatonia action
- JavaMemoryModel: PC language alert: more suggestions
- JavaMemoryModel: PDA JVM and Linux OS Crash
- JavaMemoryModel: Pentium memory model
- JavaMemoryModel: Performing speculative writes ahead of
- JavaMemoryModel: Performing speculative writes ahead of loops that may not terminate
- JavaMemoryModel: Please move JMM discussion to javamemorymodel-discussion@mimsy.cs.umd.edu
- JavaMemoryModel: Possible weakening of Manson/Pugh model
- JavaMemoryModel: Prescient reads unnecessary?
- JavaMemoryModel: prescient write question
- JavaMemoryModel: Previous discussions of final fields: final fields can only be set once in constructors
- JavaMemoryModel: Prioritizing IE without notifyAll().
- JavaMemoryModel: Problem on single processor
- JavaMemoryModel: Problem with Thread.sleep
- JavaMemoryModel: Procedural questions
- JavaMemoryModel: Programmer Oriented FAQ
- JavaMemoryModel: Proof that reordering transformation are legal
- JavaMemoryModel: Proof to show that M/P obeys SC-
- JavaMemoryModel: Properties vs. definitions vs. implementations
- JavaMemoryModel: Proposal for how to move forward on test cases 5 and 10
- JavaMemoryModel: proposal for semantics & implementation on relaxed memory model machines
- JavaMemoryModel: proposal for semantics & implementation onrelaxed memory model machines
- JavaMemoryModel: Proposal on finalizers
- JavaMemoryModel: Proposals on wait and interrupts
- JavaMemoryModel: Proposed Final Specification
- JavaMemoryModel: Proposed Test Case 18b
- JavaMemoryModel: Proposed wording on lost interrupts
- JavaMemoryModel: public or private BOF at OOPSLA?
- JavaMemoryModel: Pulling the lever on the JMM JSR
- JavaMemoryModel: Qualified this is final?
- JavaMemoryModel: Question about _current_ semantics of start
- JavaMemoryModel: Question about implementation of java.util.concurrent.ConcurrentHashMap
- JavaMemoryModel: Question about the semantics of volatile
- JavaMemoryModel: Question about the semantics of volatile (typo fix)
- JavaMemoryModel: Question about the semantics of volatile]
- JavaMemoryModel: Question about volatiles
- JavaMemoryModel: Question regarding causality
- JavaMemoryModel: Question regarding causality&In-Reply-To=<42057579.80200>
- JavaMemoryModel: Question: Why is it that Memory Models are Intuitively Hard?
- JavaMemoryModel: Questions about the proposed semantics
- JavaMemoryModel: Questions about the proposed semantics]
- JavaMemoryModel: quick opcodes unsafe under weak memory models
- JavaMemoryModel: Race-proof mutable objects and synchronized constructors
- JavaMemoryModel: Reading List for lurkers
- JavaMemoryModel: Ready for community draft of JSR133?
- JavaMemoryModel: Real-Time Core Extensions vs. the new and improved Java Memory Model
- JavaMemoryModel: real-time java spec
- JavaMemoryModel: recap on threading models
- JavaMemoryModel: recap: concurrent reads
- JavaMemoryModel: Reconsidering prioritized InterruptedExceptions
- JavaMemoryModel: Reconsidering spurious wakeups
- JavaMemoryModel: Reference on "Correctly synchronized programs are sequentially consistent"
- JavaMemoryModel: References
- JavaMemoryModel: Reflection
- JavaMemoryModel: Relaxing formalization of "causal loop" safety
- JavaMemoryModel: Relaxing SC to avoid global total orders.
- JavaMemoryModel: reminder: javaMemoryModel is archived....
- JavaMemoryModel: Removal of Synchronization on Weakly Ordered Machines
- JavaMemoryModel: Reopen Case 18?
- JavaMemoryModel: repeated email bounces may unsubscribe you from the list
- JavaMemoryModel: Replication of Problem on single processor?
- JavaMemoryModel: Reply to field cleared
- JavaMemoryModel: Reply to field on mailing list
- JavaMemoryModel: required reads and writes (was: The choice we need to make on test cases 5 and 10)
- JavaMemoryModel: Required safety guarantees in Java memory model
- JavaMemoryModel: Results of discussions with Sarita
- JavaMemoryModel: Revised JVM98 statistics
- JavaMemoryModel: Revised report on the Java Memory Model
- JavaMemoryModel: revised version of non-operational JMM paper
- JavaMemoryModel: Revisiting sleep loops and "useless" memory barriers
- JavaMemoryModel: Roach motel ordering: Do we have consensus?
- JavaMemoryModel: Roach motel volatile ordering and the optimistic readers trans
- JavaMemoryModel: Rough draft of JSR to revise Java Thread spec
- JavaMemoryModel: Rules on objects escaping their constructor
- JavaMemoryModel: Rules that guarantee "Initialization Safety"
- JavaMemoryModel: Sarita's SC-2 allows the behavior in causality test 5
- JavaMemoryModel: SC for DRF programs with Bill/Jeremy's new approach?
- JavaMemoryModel: SC or Coherence for Volatiles?
- JavaMemoryModel: SC- update
- JavaMemoryModel: SC- with better line breaks :-)
- JavaMemoryModel: Schedule for changing the Java Memory Model
- JavaMemoryModel: Schedule for changing the JMM
- JavaMemoryModel: Second call for participation in JMM workshop at OOPSLA
- JavaMemoryModel: semantics and optimization of final fields
- JavaMemoryModel: Semantics for yield and sleep
- JavaMemoryModel: Semantics musings
- JavaMemoryModel: Semantics musings [From Ramki]
- JavaMemoryModel: Semantics of final
- JavaMemoryModel: Semantics of final and fixing the immutable String problem
- JavaMemoryModel: Semantics of finalize
- JavaMemoryModel: Semantics of locks and volatiles
- JavaMemoryModel: Semantics of Multithreaded Java
- JavaMemoryModel: Semantics of volatile
- JavaMemoryModel: Semantics vs. compiler optimizations
- JavaMemoryModel: Sequential consistency
- JavaMemoryModel: Serialization and final fields
- JavaMemoryModel: Serialization and final fields - what happened?
- JavaMemoryModel: serialization and finals
- JavaMemoryModel: Shall we just punt on which classloaders are reachable?
- JavaMemoryModel: Should a read memory barrier flush a final value
- JavaMemoryModel: Should we allow synchronized constructors?
- JavaMemoryModel: Should we prohibit all causal loops?
- JavaMemoryModel: singleton q-of-week
- JavaMemoryModel: Singleton question - and not about DCL!
- JavaMemoryModel: Slides from an MIT talk I gave now available
- JavaMemoryModel: Slight simplification of semantics on System.in, System.out, System.err
- JavaMemoryModel: Small tweak to causality rules
- JavaMemoryModel: Small typo in my previous message
- JavaMemoryModel: Some C# thread code
- JavaMemoryModel: Some notes on the DB benchmark
- JavaMemoryModel: Some odds and ends
- JavaMemoryModel: Spec on on wait and interrupts
- JavaMemoryModel: specific Causality test cases
- JavaMemoryModel: Specification
- JavaMemoryModel: static singletons in C on win32
- JavaMemoryModel: status of "Multithreaded Semantics for Java, Revised"
- JavaMemoryModel: Status report
- JavaMemoryModel: Sticking with happens-before
- JavaMemoryModel: Store/load barrier
- JavaMemoryModel: String literals and String.intern()
- JavaMemoryModel: StringBuffer intensive codes/applications/benchmarks
- JavaMemoryModel: Stripped down intuitive description of my model
- JavaMemoryModel: Stronger version of SC- that forbids tests 5 and 10
- JavaMemoryModel: Stuff for new readers...
- JavaMemoryModel: Stuff on Pentium memory barriers
- JavaMemoryModel: subtle details for final fields
- JavaMemoryModel: Summary of useless sync
- JavaMemoryModel: Summary: JMM problems with latch or copy-on-write?
- JavaMemoryModel: Synchronization and the Java Memory Model
- JavaMemoryModel: Synchronization constraints due to class initialization
- JavaMemoryModel: Synchronization in the spec benchmarks
- JavaMemoryModel: Synchronization optimizations prohibited under CRF
- JavaMemoryModel: Synchronization order and finalization
- JavaMemoryModel: Synchronization overhead in Spec JVM 98
- JavaMemoryModel: test case 11; allowed by Manson/Pugh but not by SC-1
- JavaMemoryModel: Test case 15
- JavaMemoryModel: Test Case 18 variations
- JavaMemoryModel: Thanks for the notes of concern, but I don't have a virus
- JavaMemoryModel: That gap again
- JavaMemoryModel: The "Double Checked" Declaration is #1
- JavaMemoryModel: The "Double-Checked Locking is broken" declaration
- JavaMemoryModel: The choice we need to make on test cases 5 a nd 10
- JavaMemoryModel: The choice we need to make on test cases 5 and 10
- JavaMemoryModel: The final word (fat chance) on final
- JavaMemoryModel: The Intuition Is the Model - the full model is in this email!
- JavaMemoryModel: The Memory Model is _done_
- JavaMemoryModel: The Optimistic Read Idiom and the new Java Memory Model
- JavaMemoryModel: The property of "race-free implies SC"
- JavaMemoryModel: The range of memory models now in play
- JavaMemoryModel: The SC- memory model
- JavaMemoryModel: The Ucases
- JavaMemoryModel: There is _NO_ interaction between the memory model and synchronous exceptions
- JavaMemoryModel: TheServerSide.com: EJBean Class Initialization Hooks
- JavaMemoryModel: Thread model algorithm.
- JavaMemoryModel: Thread starting in constructors
- JavaMemoryModel: Thread Synchronization at Creation and Termination
- JavaMemoryModel: Thread.stop()
- JavaMemoryModel: Threading issues in my connection pool
- JavaMemoryModel: Tiger beta1 ConcurrentHashMap bug?
- JavaMemoryModel: tiny detail: intra-thread semantics or unithread semantics
- JavaMemoryModel: to hb or not to hb
- JavaMemoryModel: To race or not to race
- JavaMemoryModel: Total ordering of volatile memory operations
- JavaMemoryModel: Total orders
- JavaMemoryModel: transient final fields and deserialization
- JavaMemoryModel: Trip report from Sun East
- JavaMemoryModel: Trip report: initialization safety
- JavaMemoryModel: Tweak to rules on writes to final fields in classfiles
- JavaMemoryModel: Typo in Case 9 and Case 9a?
- JavaMemoryModel: Unexpected weakness/divergence in old JVM spec of final fields
- JavaMemoryModel: Unsynchronized gettes
- JavaMemoryModel: Unsynchronized read as an optimization
- JavaMemoryModel: Update on final fields in JVMS
- JavaMemoryModel: Update on Java Memory Model
- JavaMemoryModel: Update on JMM JSR
- JavaMemoryModel: Update on our alternative JMM specification
- JavaMemoryModel: Update to Java Memory Model spec
- JavaMemoryModel: Update to memory model
- JavaMemoryModel: Updated JMM schedule and status report
- JavaMemoryModel: Updates to M/P model
- JavaMemoryModel: Use-case for strong volatile
- JavaMemoryModel: Use-case for strong volatile interpretation
- JavaMemoryModel: Volatile and Final semantics, etc.
- JavaMemoryModel: Volatile array references
- JavaMemoryModel: volatile arrays
- JavaMemoryModel: Volatile compliance
- JavaMemoryModel: Volatile isn't used in most code
- JavaMemoryModel: Volatile spec complience tests
- JavaMemoryModel: Volatile variables in a weak memory model
- JavaMemoryModel: Volatiles - where does SC work and PO doesn'
- JavaMemoryModel: Volatiles - where does SC work and PO doesn' t
- JavaMemoryModel: Volatiles - where does SC work and PO doesn' t?
- JavaMemoryModel: Volatiles - where does SC work and PO doesn't
- JavaMemoryModel: Volatiles - where does SC work and PO doesn't?
- JavaMemoryModel: Volatiles are neither 1 way nor 2 way barrie rs
- JavaMemoryModel: Volatiles are neither 1 way nor 2 way barriers
- JavaMemoryModel: Volatiles in Sarita's model
- JavaMemoryModel: Wait/notify semantics
- JavaMemoryModel: Wait/notify semantics [revision]
- JavaMemoryModel: wait/notify/interrupt - a visible state model - FWIW
- JavaMemoryModel: Waits, Interrupts and Notify-s
- JavaMemoryModel: Way forward on JSR-133
- JavaMemoryModel: We need your litmus tests
- JavaMemoryModel: Weak fairness in the Java memory model
- JavaMemoryModel: Weak memory model implementation with final fields
- JavaMemoryModel: weak vs. strong class initialization safety
- JavaMemoryModel: What Causality test cases does the CLI/C# me mory model allow?
- JavaMemoryModel: What Causality test cases does the CLI/C# memory model allow?
- JavaMemoryModel: What do I do with volatiles?
- JavaMemoryModel: What should the SC- discontinuities be? This list should decide.
- JavaMemoryModel: What's "control dependence" mean?
- JavaMemoryModel: When are self-justifying speculative operations allowed?
- JavaMemoryModel: When can a classloader be unloaded
- JavaMemoryModel: Why CnC
- JavaMemoryModel: Why I am resisting putting data/control dependences into the semantics
- JavaMemoryModel: Why I want to prohibit test cases 5 and 10
- JavaMemoryModel: Why not delegate System.in/out/err, instead of see it as special case?
- JavaMemoryModel: Will String be secure?
- JavaMemoryModel: Will this solution work?
- JavaMemoryModel: Word tearing
- JavaMemoryModel: Word-tearing
- JavaMemoryModel: Worries about JIT compilation and class loading on multiprocessors
- JavaMemoryModel: Write - Read reordering for non-normals
- JavaMemoryModel: Write atomicity for volatiles
- JavaMemoryModel: Writing email while you're sick to your stomach
- JavaMemoryModel:(Official) Good news on IA-64
- JMM problems with latch or copy-on-write ?
- JMM problems with latch or copy-on-write?
- locks vs. volatiles
- Loops, programming languages, and weak fairness
- movement into synchronized blocks
- Oops... Forgot non-atomic volatile write s
- Oops... Forgot non-atomic volatile writes
- Ownership Types for Safe Programming (was: Disallowing badly synchronized programs)
- Question on memory models
- Question regarding nested synchronized blocks
- Question: Why is it that Memory Models are Intuitively Hard?
- Re #2: JavaMemoryModel: Problem with Thread.sleep
- recap on threading models
- Roach motel ordering: Do we have consensus?
- Schedule for changing the JavaMemoryModel
- Serialization and final fields - what happened?
- singleton of the week
- SoftReference not thread-safe ?
- spec for VM or language
- synchronized new
- There is _NO_ interaction between the memory model and synchronous exceptions
- TheServerSide.com: EJBean Class Initiali zation Hooks
- TheServerSide.com: EJBean Class Initialization Hooks
- Threading issues in my connection pool
- Total ordering of volatile memory operations
- Updated JMM
- Write atomicity for volatiles
- your message to the mailing list bounced...
Last message date: Wed Aug 24 2005 - 14:49:54 EDT
Archived on: Thu Oct 13 2005 - 07:01:13 EDT
2503 messages sorted by:
[ author ]
[ date ]
[ thread ]
About this archive
Mail actions: [ mail a new topic ]
This archive was generated by hypermail 2b29
: Thu Oct 13 2005 - 07:01:13 EDT