• 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: Looking for a Workaround for GCC Bug
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Looking for a Workaround for GCC Bug


  • Subject: Re: Looking for a Workaround for GCC Bug
  • From: Larry Bright <email@hidden>
  • Date: Fri, 16 Jan 2004 08:10:32 -0800

Alastair,

Looks like I have an earlier version of the assembler than you. I have

+ /usr/libexec/gcc/darwin/ppc/as -v -V
Apple Computer, Inc. version cctools-495.obj~4, GNU assembler version 1.38


If you're still interested I can send you the .s file later today. Right now, I'm late for an appointment, and have to run.

Thanks a 10^6 for your help. I now see light at the end of the tunnel!

Larry


On Jan 16, 2004, at 8:02 AM, Alastair Houghton wrote:

On 16 Jan 2004, at 15:58, Larry Bright wrote:


On Jan 16, 2004, at 7:46 AM, Alastair Houghton wrote:

On 16 Jan 2004, at 05:58, Larry Bright wrote:

If anyone knows a workaround for the following bug (I have reported it to Apple), I would appreciate knowing about it. I discovered this bug while developing in Xcode, but it seems trace back to the GCC compiler (version 3.3).

It seems to work just fine using GCC 3.3 20030304 (Apple Computer, Inc. build 1495). Try doing


	gcc -v

and see what your GCC comes back with.
...
  Do you have any other options enabled as well?)


Thanks for your prompt response, Alastair. Below you'll find exactly what I did in a Terminal window to get the results I reported in my original post. (Note that I AM using the same version and build of GCC that you used, according to the results of 'gcc -v'.) I can't even begin to explain why we would get different results!


Thanks again for your help. If you have any additional thoughts that might help clear up this mystery, I'd be very grateful to learn of them.

Send me a copy of the .s file that you get from

	gcc -g -S ctl.m

and I'll compare it with mine.

Also, do

	as -v -V

to check the version of the assembler we're both using; mine says:

+ /usr/libexec/gcc/darwin/ppc/as -v -V
Apple Computer, Inc. version cctools-498.obj~14, GNU assembler version 1.38


Kind regards,

Alastair.
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.

References: 
 >Looking for a Workaround for GCC Bug (From: Larry Bright <email@hidden>)
 >Re: Looking for a Workaround for GCC Bug (From: Alastair Houghton <email@hidden>)
 >Re: Looking for a Workaround for GCC Bug (From: Larry Bright <email@hidden>)

  • Prev by Date: Re: Looking for a Workaround for GCC Bug
  • Next by Date: Re: Asterisk/XCode AppleScript menu problem
  • Previous by thread: Re: Looking for a Workaround for GCC Bug
  • Next by thread: Re: Looking for a Workaround for GCC Bug
  • Index(es):
    • Date
    • Thread