Is this operation correct for chain operations?
0
I am doing an Computer Architecture project for my studies.
Among others my system should do chain operations using direct indexed addressing.
So is this operation technically correct?
REP MOVS AX, [SI]
cpu-architecture
asked Nov 14 '18 at 13:51
PyQPyQ
6
add a comment |
0
I am doing an Computer Architecture project for my studies.
Among others my system should do chain operations using direct indexed addressing.
So is this operation technically correct?
REP MOVS AX, [SI]
cpu-architecture
asked Nov 14 '18 at 13:51
PyQPyQ
6
You're inventing your own architecture, apparently, so you can use different syntax or mnemonics than x86 if you want. In x86,movscopies from memory to memory. With those operands, onlylodsreally fits for x86 (andrep lodsis weird). But sure, that syntax could make sense for your equivalent of x86'srep stos. See felixcloutier.com/x86/REP:REPE:REPZ:REPNE:REPNZ.html
– Peter Cordes
Nov 14 '18 at 14:03
@PeterCordes Thanks for your answer. Unfortunately I can't use my own syntax because lecturer doesn't accept it. So do you think that this operation should be correct? I have to have this chain operation with direct indexed addressing.
– PyQ
Nov 14 '18 at 14:42
@PeterCordes I've already been to him 3 times and always there was something that he complains. "Oh it's technically correct but I don't like it. It's not like I want it to be" and that's all
– PyQ
Nov 14 '18 at 14:43
Wait, are you actually trying to program x86, not make up your own new architecture?rep movswdoesn't touch AX, it's a memcpy from [SI] to [DI]. What do you actually want your instruction to do? (And BTW, "chain" is not a word normally used in x86 manuals.)
– Peter Cordes
Nov 14 '18 at 14:45
add a comment |
0
0
0
I am doing an Computer Architecture project for my studies.
Among others my system should do chain operations using direct indexed addressing.
So is this operation technically correct?
REP MOVS AX, [SI]
cpu-architecture
asked Nov 14 '18 at 13:51
PyQPyQ
6
I am doing an Computer Architecture project for my studies.
Among others my system should do chain operations using direct indexed addressing.
So is this operation technically correct?
REP MOVS AX, [SI]
cpu-architecture
cpu-architecture
asked Nov 14 '18 at 13:51
PyQPyQ
6
asked Nov 14 '18 at 13:51
PyQPyQ
6
asked Nov 14 '18 at 13:51
PyQPyQ
6
asked Nov 14 '18 at 13:51
PyQPyQ
6
asked Nov 14 '18 at 13:51
PyQPyQ
6
6
You're inventing your own architecture, apparently, so you can use different syntax or mnemonics than x86 if you want. In x86,movscopies from memory to memory. With those operands, onlylodsreally fits for x86 (andrep lodsis weird). But sure, that syntax could make sense for your equivalent of x86'srep stos. See felixcloutier.com/x86/REP:REPE:REPZ:REPNE:REPNZ.html
– Peter Cordes
Nov 14 '18 at 14:03
@PeterCordes Thanks for your answer. Unfortunately I can't use my own syntax because lecturer doesn't accept it. So do you think that this operation should be correct? I have to have this chain operation with direct indexed addressing.
– PyQ
Nov 14 '18 at 14:42
@PeterCordes I've already been to him 3 times and always there was something that he complains. "Oh it's technically correct but I don't like it. It's not like I want it to be" and that's all
– PyQ
Nov 14 '18 at 14:43
Wait, are you actually trying to program x86, not make up your own new architecture?rep movswdoesn't touch AX, it's a memcpy from [SI] to [DI]. What do you actually want your instruction to do? (And BTW, "chain" is not a word normally used in x86 manuals.)
– Peter Cordes
Nov 14 '18 at 14:45
add a comment |
You're inventing your own architecture, apparently, so you can use different syntax or mnemonics than x86 if you want. In x86,movscopies from memory to memory. With those operands, onlylodsreally fits for x86 (andrep lodsis weird). But sure, that syntax could make sense for your equivalent of x86'srep stos. See felixcloutier.com/x86/REP:REPE:REPZ:REPNE:REPNZ.html
– Peter Cordes
Nov 14 '18 at 14:03
@PeterCordes Thanks for your answer. Unfortunately I can't use my own syntax because lecturer doesn't accept it. So do you think that this operation should be correct? I have to have this chain operation with direct indexed addressing.
– PyQ
Nov 14 '18 at 14:42
@PeterCordes I've already been to him 3 times and always there was something that he complains. "Oh it's technically correct but I don't like it. It's not like I want it to be" and that's all
– PyQ
Nov 14 '18 at 14:43
Wait, are you actually trying to program x86, not make up your own new architecture?rep movswdoesn't touch AX, it's a memcpy from [SI] to [DI]. What do you actually want your instruction to do? (And BTW, "chain" is not a word normally used in x86 manuals.)
– Peter Cordes
Nov 14 '18 at 14:45
You're inventing your own architecture, apparently, so you can use different syntax or mnemonics than x86 if you want. In x86,
movs copies from memory to memory. With those operands, only lods really fits for x86 (and rep lods is weird). But sure, that syntax could make sense for your equivalent of x86's rep stos. See felixcloutier.com/x86/REP:REPE:REPZ:REPNE:REPNZ.html– Peter Cordes
Nov 14 '18 at 14:03
You're inventing your own architecture, apparently, so you can use different syntax or mnemonics than x86 if you want. In x86,
movs copies from memory to memory. With those operands, only lods really fits for x86 (and rep lods is weird). But sure, that syntax could make sense for your equivalent of x86's rep stos. See felixcloutier.com/x86/REP:REPE:REPZ:REPNE:REPNZ.html– Peter Cordes
Nov 14 '18 at 14:03
@PeterCordes Thanks for your answer. Unfortunately I can't use my own syntax because lecturer doesn't accept it. So do you think that this operation should be correct? I have to have this chain operation with direct indexed addressing.
– PyQ
Nov 14 '18 at 14:42
@PeterCordes Thanks for your answer. Unfortunately I can't use my own syntax because lecturer doesn't accept it. So do you think that this operation should be correct? I have to have this chain operation with direct indexed addressing.
– PyQ
Nov 14 '18 at 14:42
@PeterCordes I've already been to him 3 times and always there was something that he complains. "Oh it's technically correct but I don't like it. It's not like I want it to be" and that's all
– PyQ
Nov 14 '18 at 14:43
@PeterCordes I've already been to him 3 times and always there was something that he complains. "Oh it's technically correct but I don't like it. It's not like I want it to be" and that's all
– PyQ
Nov 14 '18 at 14:43
Wait, are you actually trying to program x86, not make up your own new architecture?
rep movsw doesn't touch AX, it's a memcpy from [SI] to [DI]. What do you actually want your instruction to do? (And BTW, "chain" is not a word normally used in x86 manuals.)– Peter Cordes
Nov 14 '18 at 14:45
Wait, are you actually trying to program x86, not make up your own new architecture?
rep movsw doesn't touch AX, it's a memcpy from [SI] to [DI]. What do you actually want your instruction to do? (And BTW, "chain" is not a word normally used in x86 manuals.)– Peter Cordes
Nov 14 '18 at 14:45
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53301815%2fis-this-operation-correct-for-chain-operations%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53301815%2fis-this-operation-correct-for-chain-operations%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You're inventing your own architecture, apparently, so you can use different syntax or mnemonics than x86 if you want. In x86,
movscopies from memory to memory. With those operands, onlylodsreally fits for x86 (andrep lodsis weird). But sure, that syntax could make sense for your equivalent of x86'srep stos. See felixcloutier.com/x86/REP:REPE:REPZ:REPNE:REPNZ.html– Peter Cordes
Nov 14 '18 at 14:03
@PeterCordes Thanks for your answer. Unfortunately I can't use my own syntax because lecturer doesn't accept it. So do you think that this operation should be correct? I have to have this chain operation with direct indexed addressing.
– PyQ
Nov 14 '18 at 14:42
@PeterCordes I've already been to him 3 times and always there was something that he complains. "Oh it's technically correct but I don't like it. It's not like I want it to be" and that's all
– PyQ
Nov 14 '18 at 14:43
Wait, are you actually trying to program x86, not make up your own new architecture?
rep movswdoesn't touch AX, it's a memcpy from [SI] to [DI]. What do you actually want your instruction to do? (And BTW, "chain" is not a word normally used in x86 manuals.)– Peter Cordes
Nov 14 '18 at 14:45