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.
