Closed Bug 54434 Opened 25 years ago Closed 25 years ago

Expunge _compare_and_swap_lock from jslock.c

Categories

(Core :: JavaScript Engine, defect, P3)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: brendan, Assigned: rogerl)

Details

There should be no global lock used to emulate compare-and-swap instructions. If the target architecture has no such atomic instruction, then jslock.c should be compiled with JS_USE_ONLY_NSPR_LOCKS (if NSPR hasn't been ported to the target arch, port it). If compiled without JS_USE_ONLY_NSPR_LOCKS, jslock.c should have a big ugly #error "Target architecture doesn't support compare and swap. Define JS_USE_ONLY_NSPR_LOCKS." or some such. /be
Let's see a patch!
I did this while fixing bug 54743, the big "lock-free operation within a request for single-threaded scopes" patch. /be
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Marking Verified -
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.