loader loads the program from disc to the memory.
who loads the program from disc to the memory?
loader
the whdload "slave" interface is integrated into the os in that you can double click a program icon to run the program at any time. when the user executes the program, by clicking a stored image icon, the amigaos operating system loads the whdload executable and starts it. then the loader checks the software and hardware environment, loads and checks the slave interface required for that chosen demo or game and allocates required memory for the installed program. if the "preload" feature is enabled into the requester page of whdload, then the program attempts to load disk images and files into ram (insofar as free memory is available).
whdload
selective memory dependence prediction stalls specific loads until it is certain that no violation may occur. it does not explicitly predict dependencies. this predictor may delay loads longer than necessary and hence result in suboptimal performance. in fact, in some cases it performs worse than naively speculating all loads as early as possible. this is because often its faster to mispeculate and recover than to wait for all preceding stores to execute. exact memory dependence prediction was developed at the university of wisconsin–madison. specifically, dynamic speculation and synchronization delays loads only as long as it is necessary by predicting the exact store a load should wait for. this predictor predicts exact dependences (store and load pair). the synonym predictor groups together all dependences that share a common load or store instruction. the store sets predictor represents multiple potential dependences efficiently by grouping together all possible stores a load may dependent upon. the store barrier predictor treats certain store instructions as barriers. that is, all subsequent load or store operations are not allowed to bypass the specific store. the store barrier predictor does not explicitly predict dependencies. this predictor may unnecessarily delay subsequent, yet independent loads. memory dependence prediction has other applications beyond the scheduling of loads and stores. for example, speculative memory cloaking and speculative memory bypassing use memory dependence prediction to streamline the communication of values through memory.
memory dependence prediction