Re: LLVM GCC 4.2 & -fno-optimize-sibling-calls FAIL
Re: LLVM GCC 4.2 & -fno-optimize-sibling-calls FAIL
- Subject: Re: LLVM GCC 4.2 & -fno-optimize-sibling-calls FAIL
- From: "David M. Cotter" <email@hidden>
- Date: Sun, 17 Jun 2012 23:58:55 -0700
that's probably it, i'm using Xcode 3.2.6 because i need to support my PPC customers.
11E53, Apple clang version 1.7 (tags/apple/clang-77) (based on LLVM 2.9svn)
On Jun 8, 2012, at 6:36 AM, Dave Zarzycki wrote:
> Newer versions of clang appear to support this flag. What version of Xcode/clang are you using?
>
>
> On Jun 7, 2012, at 11:33 PM, David M. Cotter <email@hidden> wrote:
>
>> when i was using "plain old" GCC 4.2, i could specify "-fno-optimize-sibling-calls" in "other C / C++ flags", and my stack frames would NOT be optimized out in a crash report call stack.
>>
>> since updating to LLVM, they now ARE optimized out.
>>
>> how can i get the stack frames back? i do NOT want them optimized out.
_______________________________________________
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