From: Devang Patel <dpatel@apple.com>
To: Ian Lance Taylor <iant@google.com>
Cc: Diego Novillo <dnovillo@google.com>,
GCC Mailing List <gcc@gcc.gnu.org>,
Kenneth Zadeck <zadeck@naturalbridge.com>,
Jan Hubicka <jh@suse.cz>,
Rafael Espindola <espindola@google.com>,
Ollie Wild <aaw@google.com>, Robert Hundt <rhundt@google.com>,
Nick Kledzik <kledzik@apple.com>,
Chris Lattner <clattner@apple.com>
Subject: Re: [whopr] Design/implementation alternatives for the driver and WPA
Date: Wed, 04 Jun 2008 18:48:00 -0000 [thread overview]
Message-ID: <A6562727-A612-4FEB-968B-5B9700C27738@apple.com> (raw)
In-Reply-To: <D054C487-3C4A-4BCB-A27A-513412B5837E@apple.com>
>> Also, returning a single object file restricts the possibilities.
>> The
>> design of WHOPR, as I understand it, permits creating several
>> different object files in parallel based on a fast analysis of which
>> code should be compiled together. When the linker supports
>> concurrent
>> linking, it will be desirable to be able to provide it with each
>> object file as it is completed.
By definition, inter modular optimizer (aka lto) blurs object files
boundaries. Typically, it will construct and walk combined call graph
instead of dividing work based on input files. It does not add lots of
value to preserve one to one direct relationship between optimizer
input files and output files. I agree, it makes sense to have an
additional interface to incrementally feed linker optimized chunks of
code to take advantage of concurrent linking supported by the linker.
-
Devang
next prev parent reply other threads:[~2008-06-04 18:48 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 16:46 Diego Novillo
2008-06-04 2:27 ` Chris Lattner
2008-06-04 7:28 ` Rafael Espindola
2008-06-04 16:34 ` Chris Lattner
2008-06-04 16:48 ` Rafael Espindola
2008-06-04 13:00 ` Diego Novillo
2008-06-04 15:28 ` Kenneth Zadeck
2008-06-04 15:54 ` Ian Lance Taylor
2008-06-04 16:50 ` Kenneth Zadeck
2008-06-04 17:05 ` Diego Novillo
2008-06-04 17:37 ` Ian Lance Taylor
2008-06-04 16:15 ` Chris Lattner
[not found] ` <65dd6fd50806041223l1871ecfbh384aa175c3da0645@mail.gmail.com>
2008-06-04 19:30 ` Fwd: " Ollie Wild
2008-06-04 20:03 ` Kenneth Zadeck
2008-06-04 20:30 ` Ian Lance Taylor
2008-06-04 20:56 ` Diego Novillo
2008-06-05 15:10 ` Jan Hubicka
2008-06-05 15:23 ` Diego Novillo
[not found] ` <89069638-6D2B-4AE6-ACB3-99A2B09091BA@apple.com>
2008-06-04 20:02 ` Ollie Wild
2008-06-04 23:59 ` Diego Novillo
2008-06-04 14:28 ` Ian Lance Taylor
2008-06-04 16:29 ` Chris Lattner
2008-06-04 16:41 ` Chris Lattner
2008-06-04 18:48 ` Devang Patel [this message]
2008-06-04 19:45 ` Ian Lance Taylor
2008-06-04 20:38 ` Nick Kledzik
2008-06-04 20:46 ` Ian Lance Taylor
2008-06-04 21:43 ` Nick Kledzik
2008-06-05 0:01 ` Ian Lance Taylor
2008-06-05 0:20 ` Nick Kledzik
2008-06-05 0:43 ` Ian Lance Taylor
2008-06-05 1:09 ` Nick Kledzik
2008-06-05 5:07 ` Devang Patel
2008-06-05 5:43 ` Ian Lance Taylor
2008-06-05 6:09 ` [whopr] plugin interface design Chris Lattner
2008-06-05 13:53 ` Ian Lance Taylor
2008-06-05 16:37 ` Chris Lattner
2008-06-05 17:39 ` Ian Lance Taylor
2008-06-07 18:31 ` Chris Lattner
2008-06-05 5:44 ` [whopr] Design/implementation alternatives for the driver and WPA Ian Lance Taylor
2008-06-05 8:41 ` Rafael Espindola
2008-06-05 14:00 ` Ian Lance Taylor
2008-06-05 16:44 ` Chris Lattner
2008-06-05 17:44 ` Ian Lance Taylor
2008-06-05 18:50 ` Nick Kledzik
2008-06-05 21:03 ` Ian Lance Taylor
2008-06-05 21:47 ` Chris Lattner
2008-06-06 1:22 ` Ian Lance Taylor
2008-06-07 18:34 ` Chris Lattner
[not found] ` <65dd6fd50806032310u2bda0953qb911e3ccfe3f305e@mail.gmail.com>
2008-06-04 19:29 ` Fwd: " Ollie Wild
2008-06-04 14:45 ` Ian Lance Taylor
2008-06-04 14:48 ` Diego Novillo
2008-06-04 15:28 ` Rafael Espindola
2008-06-04 16:31 ` Mark Mitchell
2008-07-04 3:31 ` Cary Coutant
2008-07-04 6:28 ` Ian Lance Taylor
2008-07-04 22:58 ` Daniel Jacobowitz
2008-07-06 7:30 ` Cary Coutant
2008-07-07 6:13 ` Ian Lance Taylor
2008-07-04 13:43 ` Rafael Espindola
2008-07-06 14:22 ` Cary Coutant
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=A6562727-A612-4FEB-968B-5B9700C27738@apple.com \
--to=dpatel@apple.com \
--cc=aaw@google.com \
--cc=clattner@apple.com \
--cc=dnovillo@google.com \
--cc=espindola@google.com \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=jh@suse.cz \
--cc=kledzik@apple.com \
--cc=rhundt@google.com \
--cc=zadeck@naturalbridge.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).