• 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: Chris Ridd <email@hidden>
  • Date: Fri, 16 Jan 2004 16:36:47 +0000

On 16/1/04 3:58 pm, Larry Bright <email@hidden> 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.

No problems here either! Try adding the -v and perhaps -save-temps flags to
see what gcc's actually doing.

[titanium:~/foo] cjr% gcc -c ctl.m -g -v
Reading specs from /usr/libexec/gcc/darwin/ppc/3.3/specs
Thread model: posix
gcc version 3.3 20030304 (Apple Computer, Inc. build 1495)
 /usr/libexec/gcc/darwin/ppc/3.3/cc1obj -quiet -v -D__GNUC__=3
-D__GNUC_MINOR__=3 -D__GNUC_PATCHLEVEL__=0 -D__APPLE_CC__=1495 -D__DYNAMIC__
ctl.m -fPIC -quiet -dumpbase ctl.m -auxbase ctl -g -version -o
/var/tmp//ccrDCHGk.s
GNU Objective-C version 3.3 20030304 (Apple Computer, Inc. build 1495)
(ppc-darwin)
        compiled by GNU C version 3.3 20030304 (Apple Computer, Inc. build
1495).
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=131072
ignoring nonexistent directory "/usr/ppc-darwin/include"
ignoring nonexistent directory "/Local/Library/Frameworks"
#include "..." search starts here:
#include <...> search starts here:
 /usr/local/include
 /usr/include/gcc/darwin/3.3
 /usr/include
End of search list.
Framework search starts here:
 /System/Library/Frameworks
 /Library/Frameworks
End of framework search list.
 /usr/libexec/gcc/darwin/ppc/as -arch ppc -o ctl.o /var/tmp//ccrDCHGk.s

> Cheers,
>
> Larry

Cheers,

Chris
_______________________________________________
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: 
 >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: Warning flag for 'if (x = y)'
  • 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