public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: Steven Bosscher <stevenb@suse.de>
Cc: Kenneth Zadeck <zadeck@naturalbridge.com>,
	 Razya Ladelsky <RAZYA@il.ibm.com>, Jan Hubicka <jh@suse.cz>,
	Ayal Zaks <ZAKS@il.ibm.com>,
	 "Berlin, Daniel" <dberlin@dberlin.org>,
	"Novillo, Diego" <dnovillo@redhat.com>,
	 gcc-patches@gcc.gnu.org,  hubicka@ucw.cz,
	Mircea Namolaru <NAMOLARU@il.ibm.com>
Subject: Re: IPA
Date: Thu, 14 Oct 2004 21:25:00 -0000	[thread overview]
Message-ID: <416EED8D.2050604@codesourcery.com> (raw)
In-Reply-To: <200410141922.50258.stevenb@suse.de>

Steven Bosscher wrote:

>On Thursday 14 October 2004 18:48, Kenneth Zadeck wrote:
>  
>
>> 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.
>>    
>>
>
>RMS has been convinced to step off his principles before (see gcc
>vs. egcsfor example), so we don't have to declare defeat before
>trying.
>
>IMO we should just work as-if we can have a streamable intermediate
>form, and show that there is serious benefit for GCC and for Free
>Software in general to have this feature.  We should gather and put
>up the numbers, and convince RMS that it's a Good Thing.
>  
>
Yes.

I have said publicly for some time now that I think that RMS is mistaken 
in this particular respect, and that a read/write interface to an 
intermediate form is an essential part of GCC's future.  Once we build 
it and demonstrate that it is useful, I am confident that it will become 
part of GCC because I do not think  RMS will not want to see GCC cede 
ground to other compilers.

-- 
Mark Mitchell
CodeSourcery, LLC
(916) 791-8304
mark@codesourcery.com

  reply	other threads:[~2004-10-14 21:20 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                   ` Mark Mitchell [this message]
2004-10-15  3:39                 ` IPA Daniel Berlin
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=416EED8D.2050604@codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=NAMOLARU@il.ibm.com \
    --cc=RAZYA@il.ibm.com \
    --cc=ZAKS@il.ibm.com \
    --cc=dberlin@dberlin.org \
    --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).