From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: pjoisha@alumni.northwestern.edu, gcc@gcc.gnu.org
Subject: Re: Re: -combine option for C++ sources
Date: Tue, 05 May 2009 11:12:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0905051106090.16587@digraph.polyomino.org.uk> (raw)
In-Reply-To: <84fc9c000905050236j128909bn6a698e4ed4265b05@mail.gmail.com>
On Tue, 5 May 2009, Richard Guenther wrote:
> 2009/5/5 Pramod Joisha <pramod_joisha@hotmail.com>:
> >
> >
> > Presently, the -combine option works only for C sources. I was
> > wondering whether there are technical reasons for not supporting it
> > for C++ sources. If not, are there plans for providing this support in
> > the near future?
>
> As LTO will obsolete -combine I do not see that -combine will be
> ever implemented for anything else besides C.
Formally there are things -combine does that LTO doesn't
(front-end-specific consistency checks across translation units,
supporting non-ELF targets). But I agree we should deprecate -combine
when LTO goes in (or better, deprecate the mechanism it uses and make the
driver transparently wrap LTO if possible); the consistency checks might
better be done through plugins, and there should be no great difficulty in
adding LTO support for non-ELF targets (that support arbitrary named
sections) if desired.
(The C++ front end should still grow some sort of support for handling
information from multiple translation units at once to implement exported
templates, but that's another matter.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2009-05-05 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 6:11 Pramod Joisha
2009-05-05 9:36 ` Richard Guenther
2009-05-05 11:12 ` Joseph S. Myers [this message]
2009-05-05 14:30 ` Ian Lance Taylor
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=Pine.LNX.4.64.0905051106090.16587@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=pjoisha@alumni.northwestern.edu \
--cc=richard.guenther@gmail.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).