On Fri, 18 Aug 2000, Joseph Carter wrote:
I do not know if there is a way to access the rest of EAX when accessing
AX, AL, etc. Not sure how endianness applies to EAX offhand (I've been up
a whole 10 minutes) but given 0x12345678 in EAX, AX may contain 0x5678
which is where the confusion
On Wed, Aug 16, 2000 at 10:27:45AM +0200, Paul Slootman wrote:
No, you have AH to access the high 16 bits of EAX, and AL for the low
16 bits of EAX. Or was that the high 8 bits of AX etc...
Here's the layout of the EAX register...
| EAX |
| | AX
On Fri, Aug 18, 2000 at 09:54:20AM -0500, Joseph Carter wrote:
On Wed, Aug 16, 2000 at 10:27:45AM +0200, Paul Slootman wrote:
No, you have AH to access the high 16 bits of EAX, and AL for the low
16 bits of EAX. Or was that the high 8 bits of AX etc...
Here's the layout of the EAX
On Tue, Aug 15, 2000 at 04:44:37PM -0700, Richard Hecker wrote:
I ran into a compiler error that I do not recognize. Instead of
spinning my wheels further with this, I was hoping someone familiar
with Intel assembly language on this list could shed some light on
what is happening here. As
On Wed 16 Aug 2000, Branden Robinson wrote:
I am not an assembly guru on any architecture, but here's what I think this
means. Please be warned that these could be the ravings of a deranged
lunatic.
Ditto.
The AX register is an old 16-bit register from 8086 days. When you're
running in
Branden Robinson [EMAIL PROTECTED] wrote:
/* the original bogomips code from the Linux kernel */
static __inline__ void delay(int loops)
{
__asm__(.align 2,0x90\n1:\tdecl %0\n\tjns 1b: :a (loops):ax);
}
You can either read the GCC FAQ or the GCC info on the details of this
problem.
But
Herbert Xu [EMAIL PROTECTED] wrote:
int bradon;
__asm__(.align 2,0x90\n1:\tdecl %0\n\tjns 1b
: =a (=brandon): 0 (loops));
Make that
int brandon;
__asm__ __volatile__(.align 2,0x90\n1:\tdecl %0\n\tjns 1b
: =a (brandon): 0 (loops));
Oh, and you should probably upgrade your
Hi;
I ran into a compiler error that I do not recognize. Instead of
spinning my wheels further with this, I was hoping someone familiar
with Intel assembly language on this list could shed some light on
what is happening here. As can be seen from the comments, it is
an ancient line that was
8 matches
Mail list logo
