• 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: Help with Xcode i386 Link problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Help with Xcode i386 Link problems


  • Subject: Re: Help with Xcode i386 Link problems
  • From: Eric Albert <email@hidden>
  • Date: Tue, 28 Mar 2006 12:34:19 -0800

On Mar 28, 2006, at 11:33 AM, Mark Thomas wrote:

void func()
{
asm {
    opcode 0x12345678
}
}

All this should do is put 0x12345678 into code fragment/text. I've entered
a rdar://4493569 for this. Being 'asm', this came from CodeWarrior world so
there might be something not quite right maybe on i386 side as the PPC side
everything resolves correctly.

It's important to note that your bug used 'opword', not 'opcode'. The difference is significant, since there doesn't appear to be any 'opcode' directive.


That said, 'opword' in CodeWarrior is the same as '.long' for gcc. Use '.long' instead and your code should work on both PowerPC and Intel.

Hope this helps,
Eric

_______________________________________________
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


  • Follow-Ups:
    • Re: Help with Xcode i386 Link problems
      • From: Mark Thomas <email@hidden>
    • Re: Help with Xcode i386 Link problems
      • From: Mark Thomas <email@hidden>
References: 
 >Re: Help with Xcode i386 Link problems (From: Mark Thomas <email@hidden>)

  • Prev by Date: Re: Extra files in the bundle
  • Next by Date: Error
  • Previous by thread: Re: Help with Xcode i386 Link problems
  • Next by thread: Re: Help with Xcode i386 Link problems
  • Index(es):
    • Date
    • Thread