public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/48094] ld: warning: section has unexpectedly large size errors in objc/obj-c++ lto
Date: Tue, 16 Jul 2013 19:12:00 -0000	[thread overview]
Message-ID: <bug-48094-4-18NLuZJQxH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48094-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48094

--- Comment #17 from Iain Sandoe <iains at gcc dot gnu.org> ---
Created attachment 30514
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30514&action=edit
proposed fix.

So the problem here is that when we bind multiple objects together (each of
which has an anonymous image_info section) LTO (unlike the system linker)
doens't know that these should be coalesced - and, TBH, I doubt we're going to
teach it about a darwin-specific section ... 

Luckily, the content of the image_info section only depends on command line
flags.

So this is a proposed solution.

1. allow the requisite ObjC flags to be recognized by lto1.

2. don't generate the image_info section in the FE instead ..

3. take note of the flag values, and (IFF there is some ObjC metadata present
in the object) emit the image_info section from the back end.

====

I've checked that this flies on Darwin12 with XCode 4.6.3 [with lto enabled] -
but I don't have the XCode 4.2 configuration on Darwin10.  

(it has also been tested on older versions of the tool-chain).

====

Mike - opinions on the solution?

others: wider testing please


  parent reply	other threads:[~2013-07-16 19:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12 17:31 [Bug lto/48094] New: " howarth at nitro dot med.uc.edu
2011-03-12 17:32 ` [Bug lto/48094] " howarth at nitro dot med.uc.edu
2011-03-12 17:49 ` iains at gcc dot gnu.org
2011-03-12 18:38 ` iains at gcc dot gnu.org
2011-03-13 12:13 ` iains at gcc dot gnu.org
2011-03-14  9:40 ` iains at gcc dot gnu.org
2011-11-14  0:05 ` iains at gcc dot gnu.org
2011-12-03 15:50 ` howarth at nitro dot med.uc.edu
2011-12-03 18:32 ` iains at gcc dot gnu.org
2011-12-05 15:25 ` howarth at nitro dot med.uc.edu
2011-12-05 15:31 ` howarth at nitro dot med.uc.edu
2011-12-05 17:24 ` iains at gcc dot gnu.org
2011-12-05 21:03 ` iains at gcc dot gnu.org
2011-12-06  0:50 ` steven at gcc dot gnu.org
2011-12-06  9:13 ` iains at gcc dot gnu.org
2012-02-12 14:44 ` iains at gcc dot gnu.org
2013-07-16 12:05 ` iains at gcc dot gnu.org
2013-07-16 19:12 ` iains at gcc dot gnu.org [this message]
2013-09-14 15:34 ` [Bug target/48094] " iains at gcc dot gnu.org
2013-09-14 15:36 ` iains at gcc dot gnu.org
2013-09-14 15:40 ` iains at gcc dot gnu.org
2013-09-15 18:32 ` mrs at gcc dot gnu.org
2014-04-07  6:41 ` dominiq at gcc dot gnu.org
2014-04-07  8:01 ` dominiq 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-48094-4-18NLuZJQxH@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: link
Be 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).