Assembly registers in 64-bit architecture

Following the answer about assembly registers' sizes:

First, what sizes are eax, ax, ah and their counterparts, in the 64-bit architecture? How to access a single register's byte and how to access all the 64-bit register's eight bytes?

I'd love attention for both x86-64 (x64) and Itanium processors.

Second, what is the correct way to use the four registers for holding the first four parameters in function calls in the new calling convention?

edited Jul 12 '18 at 10:50

phuclv

15.9k955230

asked Dec 17 '13 at 15:04

Reflection

88211025

hmm eax == 32bits ax == 16bits ah|al == 8bits, it's always like this, x64 adds new registers, back in the 16 bit days we only had ax & al & ah then when 32 bit addressing came round it was added in a way that didn't really effect how you address the 16bit or 8bit registers, the new registers in x64 (64 bit registers that overlap, eax that overlaps ax, etc) start with an r so rax rbx and so on. see here for more information.

– James
Dec 17 '13 at 15:19

add a comment |

Following the answer about assembly registers' sizes:

First, what sizes are eax, ax, ah and their counterparts, in the 64-bit architecture? How to access a single register's byte and how to access all the 64-bit register's eight bytes?

I'd love attention for both x86-64 (x64) and Itanium processors.

Second, what is the correct way to use the four registers for holding the first four parameters in function calls in the new calling convention?

edited Jul 12 '18 at 10:50

phuclv

15.9k955230

asked Dec 17 '13 at 15:04

Reflection

88211025

hmm eax == 32bits ax == 16bits ah|al == 8bits, it's always like this, x64 adds new registers, back in the 16 bit days we only had ax & al & ah then when 32 bit addressing came round it was added in a way that didn't really effect how you address the 16bit or 8bit registers, the new registers in x64 (64 bit registers that overlap, eax that overlaps ax, etc) start with an r so rax rbx and so on. see here for more information.

– James
Dec 17 '13 at 15:19

add a comment |

Following the answer about assembly registers' sizes:

First, what sizes are eax, ax, ah and their counterparts, in the 64-bit architecture? How to access a single register's byte and how to access all the 64-bit register's eight bytes?

I'd love attention for both x86-64 (x64) and Itanium processors.

Second, what is the correct way to use the four registers for holding the first four parameters in function calls in the new calling convention?

edited Jul 12 '18 at 10:50

phuclv

15.9k955230

asked Dec 17 '13 at 15:04

Reflection

88211025

Following the answer about assembly registers' sizes:

First, what sizes are eax, ax, ah and their counterparts, in the 64-bit architecture? How to access a single register's byte and how to access all the 64-bit register's eight bytes?

I'd love attention for both x86-64 (x64) and Itanium processors.

Second, what is the correct way to use the four registers for holding the first four parameters in function calls in the new calling convention?

assembly x86-64 32bit-64bit cpu-registers itanium

edited Jul 12 '18 at 10:50

phuclv

15.9k955230

asked Dec 17 '13 at 15:04

Reflection

88211025

edited Jul 12 '18 at 10:50

phuclv

15.9k955230

asked Dec 17 '13 at 15:04

Reflection

88211025

edited Jul 12 '18 at 10:50

phuclv

15.9k955230

edited Jul 12 '18 at 10:50

phuclv

15.9k955230

edited Jul 12 '18 at 10:50

phuclv

15.9k955230

asked Dec 17 '13 at 15:04

Reflection

88211025

asked Dec 17 '13 at 15:04

Reflection

88211025

asked Dec 17 '13 at 15:04

Reflection

88211025

hmm eax == 32bits ax == 16bits ah|al == 8bits, it's always like this, x64 adds new registers, back in the 16 bit days we only had ax & al & ah then when 32 bit addressing came round it was added in a way that didn't really effect how you address the 16bit or 8bit registers, the new registers in x64 (64 bit registers that overlap, eax that overlaps ax, etc) start with an r so rax rbx and so on. see here for more information.

– James
Dec 17 '13 at 15:19

add a comment |

hmm eax == 32bits ax == 16bits ah|al == 8bits, it's always like this, x64 adds new registers, back in the 16 bit days we only had ax & al & ah then when 32 bit addressing came round it was added in a way that didn't really effect how you address the 16bit or 8bit registers, the new registers in x64 (64 bit registers that overlap, eax that overlaps ax, etc) start with an r so rax rbx and so on. see here for more information.

– James
Dec 17 '13 at 15:19

hmm eax == 32bits ax == 16bits ah|al == 8bits, it's always like this, x64 adds new registers, back in the 16 bit days we only had ax & al & ah then when 32 bit addressing came round it was added in a way that didn't really effect how you address the 16bit or 8bit registers, the new registers in x64 (64 bit registers that overlap, eax that overlaps ax, etc) start with an r so rax rbx and so on. see here for more information.

– James
Dec 17 '13 at 15:19

add a comment |

1 Answer
1

active

oldest

votes

With the old name all registers remain the same size. To access 64-bit registers you use the new name with R-prefix such as rax, rbx...

Register names don't change so you just use the byte registers (al, bl, cl, dl, ah, bh, ch, dh) for the LSB and MSB of ax, bx, cx, dx like before.

There are also 8 new registers called r8-r15. You can access their LSBs by adding the suffix b (or l if you're using AMD). For example r8b, r9b... You can also use the LSB of esi, edi, esp, ebp by the names sil, dil, spl, bpl with the new REX prefix, but you cannot use it at the same time with ah, bh, ch or dh.

Likewise the new registers' lowest word or double word can be accessed through the suffix w or d.

x86_64 registers

What are the names of the new X86_64 processors registers?

Regarding the calling convention, on a specific system there's only one convention¹.

On Windows:
- RCX, RDX, R8, R9 for the first four integer or pointer arguments
- XMM0, XMM1, XMM2, XMM3 for floating point arguments
¹Since MSVC 2013 there's also a new extended convention on Windows called __vectorcall.

On Linux and other systems that follow System V AMD64 ABI, more arguments can be passed on the registers which may make function calling faster.
- The first six integer or pointer arguments are passed in registers RDI, RSI, RDX, RCX, R8, and R9
- Floating-point arguments are passed in XMM0 through XMM7

x86_64 calling conventions

Those are the most basics of x86_64. You should also read this

OTOH Itanium is a completely different architecture and has no relation to x86_64 whatsoever. It's a pure 64-bit architecture so all normal registers are 64-bit, no 32-bit or smaller version available. There are a lot of registers in it:

128 general-purpose integer registers r0 through r127, each carrying 64 value bits and a trap bit. We'll learn more about the trap bit later.

128 floating point registers f0 through f127.

64 predicate registers p0 through p63.

8 branch registers b0 through b7.

An instruction pointer, which the Windows debugging engine for some reason calls iip. (The extra "i" is for "insane"?)

128 special-purpose registers, not all of which have been given meanings. These are called "application registers" (ar) for some reason. I will cover selected register as they arise during the discussion.

Other miscellaneous registers we will not cover in this series.

https://blogs.msdn.microsoft.com/oldnewthing/20150727-00/?p=90821

Read more on What is the difference between x64 and IA-64?

edited Jul 14 '18 at 13:37

answered Dec 17 '13 at 15:18

phuclv

15.9k955230

add a comment |

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');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f20637569%2fassembly-registers-in-64-bit-architecture%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

With the old name all registers remain the same size. To access 64-bit registers you use the new name with R-prefix such as rax, rbx...

Register names don't change so you just use the byte registers (al, bl, cl, dl, ah, bh, ch, dh) for the LSB and MSB of ax, bx, cx, dx like before.

Likewise the new registers' lowest word or double word can be accessed through the suffix w or d.

x86_64 registers

What are the names of the new X86_64 processors registers?

Regarding the calling convention, on a specific system there's only one convention¹.

On Windows:
- RCX, RDX, R8, R9 for the first four integer or pointer arguments
- XMM0, XMM1, XMM2, XMM3 for floating point arguments
¹Since MSVC 2013 there's also a new extended convention on Windows called __vectorcall.

On Linux and other systems that follow System V AMD64 ABI, more arguments can be passed on the registers which may make function calling faster.
- The first six integer or pointer arguments are passed in registers RDI, RSI, RDX, RCX, R8, and R9
- Floating-point arguments are passed in XMM0 through XMM7

x86_64 calling conventions

Those are the most basics of x86_64. You should also read this

128 general-purpose integer registers r0 through r127, each carrying 64 value bits and a trap bit. We'll learn more about the trap bit later.

128 floating point registers f0 through f127.

64 predicate registers p0 through p63.

8 branch registers b0 through b7.

An instruction pointer, which the Windows debugging engine for some reason calls iip. (The extra "i" is for "insane"?)

128 special-purpose registers, not all of which have been given meanings. These are called "application registers" (ar) for some reason. I will cover selected register as they arise during the discussion.

Other miscellaneous registers we will not cover in this series.

https://blogs.msdn.microsoft.com/oldnewthing/20150727-00/?p=90821

Read more on What is the difference between x64 and IA-64?

edited Jul 14 '18 at 13:37

answered Dec 17 '13 at 15:18

phuclv

15.9k955230

add a comment |

With the old name all registers remain the same size. To access 64-bit registers you use the new name with R-prefix such as rax, rbx...

Register names don't change so you just use the byte registers (al, bl, cl, dl, ah, bh, ch, dh) for the LSB and MSB of ax, bx, cx, dx like before.

Likewise the new registers' lowest word or double word can be accessed through the suffix w or d.

x86_64 registers

What are the names of the new X86_64 processors registers?

Regarding the calling convention, on a specific system there's only one convention¹.

On Windows:
- RCX, RDX, R8, R9 for the first four integer or pointer arguments
- XMM0, XMM1, XMM2, XMM3 for floating point arguments
¹Since MSVC 2013 there's also a new extended convention on Windows called __vectorcall.

On Linux and other systems that follow System V AMD64 ABI, more arguments can be passed on the registers which may make function calling faster.
- The first six integer or pointer arguments are passed in registers RDI, RSI, RDX, RCX, R8, and R9
- Floating-point arguments are passed in XMM0 through XMM7

x86_64 calling conventions

Those are the most basics of x86_64. You should also read this

128 general-purpose integer registers r0 through r127, each carrying 64 value bits and a trap bit. We'll learn more about the trap bit later.

128 floating point registers f0 through f127.

64 predicate registers p0 through p63.

8 branch registers b0 through b7.

An instruction pointer, which the Windows debugging engine for some reason calls iip. (The extra "i" is for "insane"?)

128 special-purpose registers, not all of which have been given meanings. These are called "application registers" (ar) for some reason. I will cover selected register as they arise during the discussion.

Other miscellaneous registers we will not cover in this series.

https://blogs.msdn.microsoft.com/oldnewthing/20150727-00/?p=90821

Read more on What is the difference between x64 and IA-64?

edited Jul 14 '18 at 13:37

answered Dec 17 '13 at 15:18

phuclv

15.9k955230

add a comment |

With the old name all registers remain the same size. To access 64-bit registers you use the new name with R-prefix such as rax, rbx...

Register names don't change so you just use the byte registers (al, bl, cl, dl, ah, bh, ch, dh) for the LSB and MSB of ax, bx, cx, dx like before.

Likewise the new registers' lowest word or double word can be accessed through the suffix w or d.

x86_64 registers

What are the names of the new X86_64 processors registers?

Regarding the calling convention, on a specific system there's only one convention¹.

On Windows:
- RCX, RDX, R8, R9 for the first four integer or pointer arguments
- XMM0, XMM1, XMM2, XMM3 for floating point arguments
¹Since MSVC 2013 there's also a new extended convention on Windows called __vectorcall.

On Linux and other systems that follow System V AMD64 ABI, more arguments can be passed on the registers which may make function calling faster.
- The first six integer or pointer arguments are passed in registers RDI, RSI, RDX, RCX, R8, and R9
- Floating-point arguments are passed in XMM0 through XMM7

x86_64 calling conventions

Those are the most basics of x86_64. You should also read this

128 general-purpose integer registers r0 through r127, each carrying 64 value bits and a trap bit. We'll learn more about the trap bit later.

128 floating point registers f0 through f127.

64 predicate registers p0 through p63.

8 branch registers b0 through b7.

An instruction pointer, which the Windows debugging engine for some reason calls iip. (The extra "i" is for "insane"?)

128 special-purpose registers, not all of which have been given meanings. These are called "application registers" (ar) for some reason. I will cover selected register as they arise during the discussion.

Other miscellaneous registers we will not cover in this series.

https://blogs.msdn.microsoft.com/oldnewthing/20150727-00/?p=90821

Read more on What is the difference between x64 and IA-64?

edited Jul 14 '18 at 13:37

answered Dec 17 '13 at 15:18

phuclv

15.9k955230

With the old name all registers remain the same size. To access 64-bit registers you use the new name with R-prefix such as rax, rbx...

Register names don't change so you just use the byte registers (al, bl, cl, dl, ah, bh, ch, dh) for the LSB and MSB of ax, bx, cx, dx like before.

Likewise the new registers' lowest word or double word can be accessed through the suffix w or d.

x86_64 registers

What are the names of the new X86_64 processors registers?

Regarding the calling convention, on a specific system there's only one convention¹.

On Windows:
- RCX, RDX, R8, R9 for the first four integer or pointer arguments
- XMM0, XMM1, XMM2, XMM3 for floating point arguments
¹Since MSVC 2013 there's also a new extended convention on Windows called __vectorcall.

On Linux and other systems that follow System V AMD64 ABI, more arguments can be passed on the registers which may make function calling faster.
- The first six integer or pointer arguments are passed in registers RDI, RSI, RDX, RCX, R8, and R9
- Floating-point arguments are passed in XMM0 through XMM7

x86_64 calling conventions

Those are the most basics of x86_64. You should also read this

128 general-purpose integer registers r0 through r127, each carrying 64 value bits and a trap bit. We'll learn more about the trap bit later.

128 floating point registers f0 through f127.

64 predicate registers p0 through p63.

8 branch registers b0 through b7.

An instruction pointer, which the Windows debugging engine for some reason calls iip. (The extra "i" is for "insane"?)

128 special-purpose registers, not all of which have been given meanings. These are called "application registers" (ar) for some reason. I will cover selected register as they arise during the discussion.

Other miscellaneous registers we will not cover in this series.

https://blogs.msdn.microsoft.com/oldnewthing/20150727-00/?p=90821

Read more on What is the difference between x64 and IA-64?

edited Jul 14 '18 at 13:37

answered Dec 17 '13 at 15:18

phuclv

15.9k955230

edited Jul 14 '18 at 13:37

answered Dec 17 '13 at 15:18

phuclv

15.9k955230

answered Dec 17 '13 at 15:18

phuclv

15.9k955230

answered Dec 17 '13 at 15:18

phuclv

15.9k955230

add a comment |

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');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

Search This Blog

Ufyukyu