• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: __rlwinm weirdness
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: __rlwinm weirdness


  • Subject: Re: __rlwinm weirdness
  • From: Chris Espinosa <email@hidden>
  • Date: Fri, 17 Feb 2006 14:00:14 -0800

On Feb 17, 2006, at 1:46 PM, Mark Thomas wrote:

Hi,
  Moving some code over from CodeWarrior, and the follow

result = __rlwinm( theValue,8, 0, 31 )

  Doesn't work the same if compiled on CodeWarrior as if theValue =
0x11223344, result will be 0x22334411.

  But if I execute the same code in Xcode and debugging the same thing
doesn't happen which is weird, any reason why ?

In Mac OS X's headers, __rlwinm is implemented as a macro expansion. If you happen to have a local with the name "val" it will collide with the placeholder in the macro and produce unexpected results.


Chris

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >__rlwinm weirdness (From: Mark Thomas <email@hidden>)

  • Prev by Date: Re: C++ Headers in /usr/include
  • Next by Date: Re: Xcode running on Intel vs PPC
  • Previous by thread: __rlwinm weirdness
  • Next by thread: Re: Source trees don't work any more
  • Index(es):
    • Date
    • Thread