public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/48108] New: lto should be containerized in a single mach-o section on darwin Date: Mon, 14 Mar 2011 03:07:00 -0000 [thread overview] Message-ID: <bug-48108-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48108 Summary: lto should be containerized in a single mach-o section on darwin Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto AssignedTo: unassigned@gcc.gnu.org ReportedBy: howarth@nitro.med.uc.edu The LTO support on darwin has been disabled... Author: mrs Date: Mon Mar 14 02:47:49 2011 New Revision: 170929 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=170929 Log: 2011-03-13 Jack Howarth <howarth@bromo.med.uc.edu> PR lto/48086 * configure.ac: Disable LTO on darwin due to an assembler change in Xcode 3.2.6/4.0 that limits the total number of sections/segments to under 256. * configure: Regenerate. Modified: trunk/ChangeLog trunk/configure trunk/configure.ac due to the mishandling of <rdar://problem/7920267>, possible assembler bug exposed by LTO, by the Apple assembler developer where a solid 255 limit has been now imposed on all the sections= possible in a mach-o object file. This breaks the current implementation in gcc/lto/lto-object.c which relied on the ability to have an unlimited number of symbol-less GNU_LTO sections at the end of the object file. The darwin LTO support in gcc/lto/lto-object.c and gcc/config/darwin.c needs to be written to containerize all of these GNU_LTO sections into a single mach-o section. Hopefully this can be done without having to resort to an elf container, which would introduce an undesired dependency on libelf for FSF gcc on darwin.
next reply other threads:[~2011-03-14 3:07 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-14 3:07 howarth at nitro dot med.uc.edu [this message] 2011-03-14 3:10 ` [Bug lto/48108] " howarth at nitro dot med.uc.edu 2011-03-14 3:13 ` mikestump at comcast dot net 2011-03-14 9:01 ` iains at gcc dot gnu.org 2011-03-14 11:26 ` [Bug target/48108] " rguenth at gcc dot gnu.org 2011-03-14 23:34 ` mikestump at comcast dot net 2011-03-17 12:04 ` howarth at nitro dot med.uc.edu 2011-05-30 12:11 ` vincenzo.innocente at cern dot ch 2011-05-30 12:26 ` dominiq at lps dot ens.fr 2011-05-30 12:58 ` vincenzo.innocente at cern dot ch 2011-05-30 13:12 ` dominiq at lps dot ens.fr 2011-05-30 15:17 ` howarth at nitro dot med.uc.edu 2011-05-30 15:22 ` howarth at nitro dot med.uc.edu 2011-05-30 16:02 ` iains at gcc dot gnu.org 2011-07-07 10:23 ` iains at gcc dot gnu.org 2011-07-08 10:34 ` iains at gcc dot gnu.org 2011-07-08 11:20 ` howarth at nitro dot med.uc.edu 2011-07-10 4:41 ` fang at csl dot cornell.edu 2011-08-05 18:52 ` howarth at nitro dot med.uc.edu 2011-08-09 12:59 ` iains at gcc dot gnu.org 2011-09-25 9:57 ` iains at gcc dot gnu.org 2011-09-26 2:16 ` howarth at nitro dot med.uc.edu 2011-09-27 14:56 ` howarth at nitro dot med.uc.edu 2011-10-26 12:39 ` iains at gcc dot gnu.org 2011-10-26 13:29 ` howarth at nitro dot med.uc.edu 2011-11-13 16:10 ` iains at gcc dot gnu.org 2011-11-13 16:11 ` iains at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-48108-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).