public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven 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, 06 Dec 2011 00:50:00 -0000	[thread overview]
Message-ID: <bug-48094-4-TpSPLNiaSF@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

Steven Bosscher <steven at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |steven at gcc dot gnu.org

--- Comment #13 from Steven Bosscher <steven at gcc dot gnu.org> 2011-12-06 00:49:26 UTC ---
(In reply to comment #12)
> I guess, ideally, the ObjC meta-data should be re-created after LTO has done
> its magic -- but that's def. not a stage 3 type job ...

Ideally from what point of view? Certainly not that of one where there is
proper separation between front ends and the middle end. There are no language
specific post optimization passes. From the point of view of the LTO front end,
whatever the ObjC-family front ends have handed over is language independent.

But those two L_OBJC_ImageInfo variables have a number appended. Is that
supposed to be so? Or is this LTO declaration merging at work and maybe you
want to avoid that?
(Maybe I'm talking completely non-sense, but something like that came up for
PR47259 also...)


  parent reply	other threads:[~2011-12-06  0:50 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 [this message]
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
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-TpSPLNiaSF@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).