• State Not Answered
  • Locked Locked
  • Replies 18 replies
  • Subscribers 22 subscribers
  • Views 6842 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Problem with Shift-Operator

Gunnar Bohlen

Hi,

I have a Problem with the Shift-Operator >> within my C-Code.
I'm using PK166 V4.2
The following code should set the Variable n to 0.

void main()
{
 unsigned char n;
 unsigned char p;  // dummy

 n=255;
 n=n>>22;

 p=0;		// dummy

}

With Simulator and real hardware n=3!

The Compiler generates a shift of 22, which is invalid. The Assembler Opcode only evaluates the lower 4 bits of the shift-operand.

Generated Assembler Code:
R4 contains the variable n:

 MOV R5, #0x16 // incorrect Opcode???
 SHR R4,R5

The lower 4 bits of 0x16=0x06, and that is what really happens. ( 255 >> 6 = 3 )

I get the same result with Compiler V5.04.

Is it invalid to shift a byte-variable more than 8 times?
If so, why does the compiler not generate a warning?

Parents
  • 0 in reply to erik malund

    "if I shift something with a value of x that means to me that I am shifting x places."

    And for right-shifts, that works as expected when the value being shifted is unsigned or signed and is positive. It is up to the compiler implementer how to handle a signed negative value's sign bit when shifting right. The implementer is expected to handle it in a documented, defined manner of their choice.

Reply
  • 0 in reply to erik malund

    "if I shift something with a value of x that means to me that I am shifting x places."

    And for right-shifts, that works as expected when the value being shifted is unsigned or signed and is positive. It is up to the compiler implementer how to handle a signed negative value's sign bit when shifting right. The implementer is expected to handle it in a documented, defined manner of their choice.

Children
No data