• 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
LLVM GCC 4.2 & -fno-optimize-sibling-calls FAIL
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

LLVM GCC 4.2 & -fno-optimize-sibling-calls FAIL


  • Subject: LLVM GCC 4.2 & -fno-optimize-sibling-calls FAIL
  • From: "David M. Cotter" <email@hidden>
  • Date: Thu, 07 Jun 2012 23:33:03 -0700

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

  • Follow-Ups:
    • Re: LLVM GCC 4.2 & -fno-optimize-sibling-calls FAIL
      • From: Dave Zarzycki <email@hidden>
  • Prev by Date: Re: Buil Products Path
  • Next by Date: Dont found option 'stop automatically running scheme'
  • Previous by thread: Re: Buil Products Path
  • Next by thread: Re: LLVM GCC 4.2 & -fno-optimize-sibling-calls FAIL
  • Index(es):
    • Date
    • Thread