[Issue 6607] critical_.d and critical.c use double check locking the wrong way

d-bugmail at puremagic.com d-bugmail at puremagic.com
Tue Sep 6 11:27:56 PDT 2011


http://d.puremagic.com/issues/show_bug.cgi?id=6607


Sean Kelly <sean at invisibleduck.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |sean at invisibleduck.org


--- Comment #1 from Sean Kelly <sean at invisibleduck.org> 2011-09-06 11:27:42 PDT ---
I've always hoped that because Walter implemented this module, he did so
knowing how DMD would generate the involved code.  I do agree that this isn't a
safe long-term assumption though, since the compiler may change, leaving the
need to update this code as a forgotten detail.

What should really happen is for all the .c modules to be transitioned to .d
modules, and for any questionable practices like these to be changed to
something more universally reliable.  Between new language features and
core.atomic I think this can be improved without actually sacrificing
performance.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------


More information about the Digitalmars-d-bugs mailing list