linux-origin
[Top] [All Lists]

Re: broken compiler?

To: kanoj@xxxxxxxxxxxxxxxxxxx (Kanoj Sarcar)
Subject: Re: broken compiler?
From: kanoj@xxxxxxxxxxxxxxxxxxx (Kanoj Sarcar)
Date: Tue, 28 Mar 2000 14:41:57 -0800 (PST)
Cc: linux-origin@xxxxxxxxxxx
In-reply-to: <200003282236.OAA58828@google.engr.sgi.com> from "Kanoj Sarcar" at Mar 28, 2000 02:36:19 PM
Sender: owner-linux-origin@xxxxxxxxxxx
> 
> Seems like for the mips64 port, though we have big endian format within
> a word, when we do double word operations, the lower addressed word
> holds the contents of the most significant word ... ie, the significance
> is swapped. 
> 
> Is this architecture defined, or is there a register that needs to be
> programmed somewhere?
> 
> Kanoj
> 
> Ps: Example
> 
> volatile unsigned int test_lock = 0xabc;
> volatile unsigned int test_lock3 = 0x789;
> 
> If I load the dword at address &test_lock (which is a dword aligned addr),
> I get 0x78900000abc
> 

I am going nuts. The above should read:

volatile unsigned int test_lock2 = 0x123;
volatile unsigned int test_lock = 0xabc;
volatile unsigned int test_lock3 = 0x789;

If I load the dword at address &test_lock (which is a dword aligned addr),
I get 0xabc00000789. I was expecting 0x78900000abc.

Kanoj

<Prev in Thread] Current Thread [Next in Thread>