On Tue, Mar 12, 2013 at 07:31:59AM -0700, Travisseal wrote: > > Dear enthusiasts, > I am having a rough time visualizing the mechanisms that translate > compiled code into binary instructions. Most resources use very vague > language, like "fetch" and "execute". Although these are primitive > instructions, they are still abstract. How does this "fetch" go about > driving down a bus, picking up elections stored in a memory cells, and > translating them into something useful?(keep in mind hisenburg principal)
Sounds like quite a homework assignment. And no wonder you're having trouble with it, you're trying to handle too many levels of stuff at once. And it's all mixed between metaphor, model and reality. It's like trying to use organic chemistry to understand traffic laws. So break it down, understand each level separately. Understand what's a metaphor, what's a model and what's real. And stay out of the solid-state physics for now, that stuff's ugly. > Call me faithless, but can someone provide me material that goes this deep. Sure, it's called "earning an electrical engineering degree" :) I did that a few years ago at PSU. Takes a while. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
