Linked by Thom Holwerda on Thu 26th Jan 2006 18:08 UTC, submitted by Sebastian Schildt
Permalink for comment 89856
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2005-11-11
I've done a lot of x86 assembly programming in my day, but I'm wondering what "fast call" means. To me a call is CALL <proc> (or INT xx, which is anything but fast, and you wouldn't want to do that in Windows -- grin). I understand the idea of protected-mode calls that involve the CPU performing a lookup into the global and/or local descriptor tables (and I've done some neat things with them back in the old EMM386.EXE days). Does the fast call concept have to do with this?