public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Romain Geissler <romain.geissler@amadeus.com>,
	Jeff Law <law@redhat.com>, 	Andi Kleen <ak@linux.intel.com>,
	GCC Development <gcc@gcc.gnu.org>
Subject: Re: [EXT] Re: Can LTO minor version be updated in backward compatible way ?
Date: Mon, 22 Jul 2019 11:20:00 -0000	[thread overview]
Message-ID: <CAFiYyc0e7vuaQyMgc31i6Xa19qfiu5bJGoqKDXid=Wog6QoqUw@mail.gmail.com> (raw)
In-Reply-To: <87wogas4l0.fsf@oldenburg2.str.redhat.com>

On Mon, Jul 22, 2019 at 1:15 PM Florian Weimer <fweimer@redhat.com> wrote:
>
> * Richard Biener:
>
> > On Fri, Jul 19, 2019 at 10:30 AM Florian Weimer <fweimer@redhat.com> wrote:
> >>
> >> * Romain Geissler:
> >>
> >> > That may fly in the open source world, however I expect some vendors
> >> > shipping proprietary code might be fine with assembly/LTO
> >> > representation of their product, but not source.
> >>
> >> They can't ship LTO today anyway due to the format incompatibility, so
> >> that's not really an argument against source-based LTO.
> >
> > Source-based LTO doesn't really work unless you can re-synthesize
> > source from the IL.  At least I don't see how you can do whole-program
> > analysis on source and then cut it into appropriate pieces, duplicating
> > some things and some not to make up for the parallel final compile step.
>
> Oh, I meant using source code only as a portable serialization of the
> program, instead of serializing unstable, compiler-specific IR.  If the
> whole program does not fit into memory, the compiler will still have to
> maintain on-disk data structures, but at least there wouldn't a
> compatibility aspect to those anymore.

OK, but then we'd need to re-do the compile and IPA analysis stage
at each link with the appropriate frontend.  But sure, that would be
possible.

Richard.

> Thanks,
> Florian

  reply	other threads:[~2019-07-22 11:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17 14:12 Romain Geissler
2019-07-17 16:15 ` Michael Matz
2019-07-17 17:30 ` Andi Kleen
2019-07-17 18:10   ` Jeff Law
2019-07-18 16:13     ` Florian Weimer
2019-07-18 23:00       ` [EXT] " Romain Geissler
2019-07-19  8:30         ` Florian Weimer
2019-07-22  7:52           ` Richard Biener
2019-07-22 11:15             ` Florian Weimer
2019-07-22 11:20               ` Richard Biener [this message]
2019-07-22 14:25     ` Martin Liška
2019-07-22 14:31       ` Jeff Law
2019-07-23  8:49         ` Martin Liška
2019-07-23 13:17           ` Jeff Law
2019-07-22 17:57     ` Jeffrey Walton
2019-07-18 11:40   ` Richard Biener

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='CAFiYyc0e7vuaQyMgc31i6Xa19qfiu5bJGoqKDXid=Wog6QoqUw@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=ak@linux.intel.com \
    --cc=fweimer@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=romain.geissler@amadeus.com \
    /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).