I see quite a few interesting perl-internals and computer science reasons discussed as to why that would be difficult (if not impossible) to do well. However, I hadn't seen any x86 arguments.
I used to be an x86 assembly programmer, so here's my take on it. (Note: my last asm programming was for a Pentium Pro, so the newer chips may have much-improved timings. Though I doubt that it would be enough to help...)
In those days, at any rate, you can execute a simple locking construct in just a few ticks. Just getting to the exception handler took many times more ticks. Then doing the page table manipulations: those were/are expensive operations also. So even if you are able to solve the other issues raised ... it would be slower rather than faster. It could make for shorter, simpler code for the user ... but timing wise, it's a dog.
In reply to Re: A faster?, safer, user transparent, shared variable "locking" mechanism.
by roboticus
in thread A faster?, safer, user transparent, shared variable "locking" mechanism.
by BrowserUk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |