public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Kenneth Zadeck <zadeck@naturalbridge.com>
Cc: Razya Ladelsky <RAZYA@il.ibm.com>, Jan Hubicka <jh@suse.cz>,
	 Ayal Zaks <ZAKS@il.ibm.com>,
	"Novillo, Diego" <dnovillo@redhat.com>,
	 gcc-patches@gcc.gnu.org, hubicka@ucw.cz,
	 Mircea Namolaru <NAMOLARU@il.ibm.com>,
	Steven Bosscher <stevenb@suse.de>
Subject: Re: IPA
Date: Fri, 15 Oct 2004 03:39:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.60.0410142306440.5482@dberlin.org> (raw)
In-Reply-To: <416EADEA.2030406@naturalbridge.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1235 bytes --]



On Thu, 14 Oct 2004, Kenneth Zadeck wrote:

> If you look at most other optimizing compilers (i.e. sun, ibm, llvm),
> they have enhanced .o formats that contain the intermediate code that can
> then be further optimized.  This solves a huge number of legistical
> problems, such as getting the user to change their entire build
> procedures and makefiles.  All you have to do is add a few options onto
> the link command.  It also means that if a single file changes, all you
> do is recompile the one file and do a (notably more expensive) link. 
> 
> The other benefit is that since a fair amount of the analysis is done
> locally before you do the intermodular stuff, it is generally faster to
> rebuild after small changes to a single file.
> 
> However, this violates one of the stallman principals of not wanting to
> have a defined api for the intermediate form of the compiler.  So we are
> forced to do something that is inferior and that, most likely, will not
> be widely used.

Except that when it becomse necsesary to do this, we'll simply do it, and 
stallman has said that would be okay.
Or so i'm told.
He just doesn't want us doing it unless it absoultely necessary to keep 
gcc competitive.

  parent reply	other threads:[~2004-10-15  3:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-10 15:38 [tree-profiling-branch PATCH] Function cloning + IPCP extension (RESUBMISSION) Razya Ladelsky
2004-10-10 17:10 ` Steven Bosscher
2004-10-10 21:25   ` Jan Hubicka
2004-10-10 23:00     ` IPA (was: Re: [tree-profiling-branch PATCH] Function cloning + IPCP extension (RESUBMISSION)) Steven Bosscher
2004-10-10 23:34       ` Jan Hubicka
2004-10-12 14:22         ` IPA Kenneth Zadeck
2004-10-12 14:41           ` IPA Jan Hubicka
     [not found]             ` <OF392747EC.15519132-ONC2256F2D.00576111-C2256F2D.005769AD@il.ibm.com>
2004-10-14 16:44               ` IPA Jan Hubicka
2004-10-14 17:22               ` IPA Kenneth Zadeck
     [not found]               ` <416EADEA.2030406@naturalbridge.com>
2004-10-14 17:24                 ` IPA Steven Bosscher
2004-10-14 21:25                   ` IPA Mark Mitchell
2004-10-15  3:39                 ` Daniel Berlin [this message]
2004-10-12 14:18 ` [tree-profiling-branch PATCH] Function cloning + IPCP extension (RESUBMISSION) Jan Hubicka

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.60.0410142306440.5482@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=NAMOLARU@il.ibm.com \
    --cc=RAZYA@il.ibm.com \
    --cc=ZAKS@il.ibm.com \
    --cc=dnovillo@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=jh@suse.cz \
    --cc=stevenb@suse.de \
    --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).