• State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 22 subscribers
  • Views 1581 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

Possible compilator bug???

Jirka Saibiuk

Hi,
i need to XOR couple of bytes. Im try to do it by this way:

	 	pozice =0;
  		adresa = 0x0A;
		data = 0x3F;
		data2 = 0x10;
		xdat =adresa ^ data ^ data2;
		//xdat = 0x25;

but the output is not XOR of this data.
I also find another interest thing:
	 	pozice =0;
  		adresa = 0x0A;
		data = 0x3F;
		data2 = 0x10;
		xdat = adresa;
		xdat ^= data ;
		xdat ^= data2;//adresa ^ data ^ data2;
		xdat = 0x25;
In xdat isnt 0x25. I currently havent JTAG and RS232 working, so i dont know the value of xdat, but im %100 sure that is not 0x25. If I commented xdat = adresa, xdat ^= data(2).... its working. Otherwise this way of xoring data its not working also.

Jirka

Parents
  • 0 in reply to erik malund

    It only takes about 5 minutes to see that what the Keil debugger is displaying and what is actually happening do not match up (This has been since the switch to realview). The compiler seems to be generating valid code for me. The (current) debugger is always confused as to where local variables and parameter are and where a line compiled code starts and ends in assembly. This is even with optimizations on the lowest setting.

Reply
  • 0 in reply to erik malund

    It only takes about 5 minutes to see that what the Keil debugger is displaying and what is actually happening do not match up (This has been since the switch to realview). The compiler seems to be generating valid code for me. The (current) debugger is always confused as to where local variables and parameter are and where a line compiled code starts and ends in assembly. This is even with optimizations on the lowest setting.

Children