public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: gcc-patches@gcc.gnu.org, rguenther@suse.de, hongjiu.lu@intel.com,
	ccoutant@google.com, iant@google.com
Subject: Re: [RFC] Getting LTO incremental linking work
Date: Thu, 26 Nov 2015 01:55:00 -0000	[thread overview]
Message-ID: <20151126005438.GJ8438@tassilo.jf.intel.com> (raw)
In-Reply-To: <20151126003828.GH20593@kam.mff.cuni.cz>

> > In theory we could change the build system to avoid that case though, but
> > it would need some changes.
> > 
> > It would be better if that could be handled somehow.
> 
> How does this work with your patchset?  Ideally we should have way to claim
> only portions of object files, but we don't have that. If we claim the file,
> the symbols in real symbol table are not visible.

It works with HJ's Linux binutils. It handles LTO and non LTO separately.

> I suppose we could play a games here with slim LTO: claim the file, see if
> there are any symbols defined in the non-LTO symbol table and if so, interpret
> read the symbol table and tell linker about the symbols and at the very end
> include the offending object file in the list of objects returned back to
> linker.
> 
> The linker then should take the symbols it wants.  There would be some fun
> involved, because the resolution info we get will consider the symbols
> defined in that object file to be IR which would need to be compensated for.

Yes something like that would be needed.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only

  reply	other threads:[~2015-11-26  0:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25  9:04 Jan Hubicka
2015-11-25 11:19 ` Richard Biener
2015-11-25 15:45   ` H.J. Lu
2015-11-25 19:21     ` Jan Hubicka
2015-11-25 23:09       ` Jan Hubicka
2015-11-25 23:56         ` Jan Hubicka
2015-11-28 10:35         ` Tom de Vries
2015-11-28 12:03           ` Tom de Vries
2015-11-28 16:05             ` Ilya Verbin
2015-11-28 17:41               ` Tom de Vries
2015-11-29 21:15                 ` Jan Hubicka
2015-11-25 18:54   ` Jan Hubicka
2015-11-26 10:15     ` Richard Biener
2015-11-26 20:30       ` Jan Hubicka
2015-11-25 23:59   ` Andi Kleen
2015-11-26  0:24 ` Andi Kleen
2015-11-26  0:54   ` Jan Hubicka
2015-11-26  1:55     ` Andi Kleen [this message]
2015-11-26  2:02       ` Jan Hubicka
2015-11-26  2:12         ` Andi Kleen
2015-11-26  6:33           ` Jan Hubicka
2015-11-26 10:33     ` Richard Biener
2016-03-16 17:33 ` H.J. Lu

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=20151126005438.GJ8438@tassilo.jf.intel.com \
    --to=ak@linux.intel.com \
    --cc=ccoutant@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hongjiu.lu@intel.com \
    --cc=hubicka@ucw.cz \
    --cc=iant@google.com \
    --cc=rguenther@suse.de \
    /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).