A question in my textbook:
Why call CS code segment? Why call SS stack segment?
It's difficult to answer.
I think just the men who create 8086/8088 CPU could answer it.
Why call CS Code Segment?
Why call CS Code Segment?
Just For Fun
Re: Why call CS Code Segment?
Not really. But since it's a question in your textbook (i.e., homework), I am reluctant to answer them other than with a counter-question (so you get a chance to reach the solution by yourself):
What is the instruction pointer?
What is the stack pointer?
What is the instruction pointer?
What is the stack pointer?
Every good solution is obvious once you've found it.
-
DeletedAccount
- Member
- Posts: 566
- Joined: Tue Jun 20, 2006 9:17 am
Re: Why call CS Code Segment?
(C)ode (S)egment => CS
(S)tack (S)egment => SS
Mu ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha
(S)tack (S)egment => SS
Mu ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha ha
Re: Why call CS Code Segment?
Hi,
Cheers,
Brendan
I think that at the time 8086 was being created, the names "foo" and "bar" had already been taken...david wrote:Why call CS code segment? Why call SS stack segment?
Cheers,
Brendan
For all things; perfection is, and will always remain, impossible to achieve in practice. However; by striving for perfection we create things that are as perfect as practically possible. Let the pursuit of perfection be our guide.
Re: Why call CS Code Segment?
Brendan wrote:Hi,
I think that at the time 8086 was being created, the names "foo" and "bar" had already been taken...david wrote:Why call CS code segment? Why call SS stack segment?
Cheers,
Brendan