Hi!
According to the SYSTEM V APPLICATION BINARY INTERFACE,
Intel386 Architecture:
ecx and edx: Scratch registers have no specified role in the standard calling
sequence. Functions do not have to preserve their values for the
caller.
Thanks for confirming.
From: Tian Kevin [EMAIL PROTECTED]
Register %ebx serves as the global offset table base register
for position-independent code. For absolute code, %ebx serves
as a local register and has no specified role in the function
calling sequence. In either case, a function must preserve the
register
Hi!
From: Tian Kevin [EMAIL PROTECTED]
Register %ebx serves as the global offset table base register
for position-independent code. For absolute code, %ebx serves
as a local register and has no specified role in the function
calling sequence. In either case, a function must preserve the
: Pavel Machek [mailto:[EMAIL PROTECTED]
Sent: 2007年6月1日 18:17
To: Zhang, Rui
Cc: linux-acpi@vger.kernel.org; [EMAIL PROTECTED]; Tian, Kevin
Subject: Re: [PATCH]: ACPI: preserve the ebx value in acpi_copy_wakeup_routine
Hi!
From: Tian Kevin [EMAIL PROTECTED]
Register %ebx serves as the global
