• 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
Xcode 3.2.6/4.0 assembler bug?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Xcode 3.2.6/4.0 assembler bug?


  • Subject: Xcode 3.2.6/4.0 assembler bug?
  • From: Jack Howarth <email@hidden>
  • Date: Sat, 12 Mar 2011 19:50:41 -0500

  It appears that the assembler in Xcode 3.2.6/4.0 now blindly enforces
the 255 limit on sections regardless of whether any of those sections actually
contain symbols. This has unfortunately broken the darwin LTO support added
to FSF gcc 4.6.0 so any users wanting to use that will have to stick with
Xcode 3.2.5. I've filed this as radar Problem ID: 9126174, "Xcode assembler
restricts number of GNU_LTO sections". Looking at the failing testcases
like...

    as -arch i386 -force_cpusubtype_ALL -o builtin-attr-1.o builtin-attr-1.s

,when compiled with Xcode 3.2.5, using MachOView shows all of the _GUN_LTO
sections containing only the intermediate GIMPLE code used for LTO and no
symbols. It is really quite unfortunate that a year's work on LTO is
rendered useless in this way. It will likely require a major rewrite of how
LTO is handled on darwin which likely won't happen until FSF gcc 4.7.
             Jack
 _______________________________________________
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

  • Prev by Date: Re: Xcode 4 related questions
  • Next by Date: Re: Xcode 4 related questions
  • Previous by thread: Re: Xcode-users Digest, Vol 8, Issue 45
  • Next by thread: Xcode 4 Documentation
  • Index(es):
    • Date
    • Thread