From: fche@redhat.com (Frank Ch. Eigler)
To: David Edelsohn <dje@watson.ibm.com>
Cc: Diego Novillo <dnovillo@redhat.com>,
Mark Mitchell <mark@codesourcery.com>,
Benjamin Kosnik <bkoz@redhat.com>,
Gabriel Dos Reis <gdr@integrable-solutions.net>,
"pcarlini@unitus.it" <pcarlini@unitus.it>,
"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc@gcc.gnu.org
Subject: Re: merging for 3.4 (was Re: [Patch] Qualify min(), max() ...)
Date: Fri, 06 Dec 2002 12:40:00 -0000 [thread overview]
Message-ID: <o5znrj7x10.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <200212041946.OAA22968@makai.watson.ibm.com>
David Edelsohn <dje@watson.ibm.com> writes:
> [...]
> Diego> I see two possible scenarios regarding optimization:
>
> Diego> (a) We merge the infrastructure with the optimizers disabled and
> Diego> keep working on them in mainline. This has the advantage of
> Diego> exposing the code for more testing, but it might disrupt
> Diego> development.
> [...]
>
> I would prefer (a) because that allows Tree-SSA to be a GCC
> technology preview in the GCC 3.4 release to which improvements can be
> merged in during later Stages of GCC 3.4 development. [...]
Another possible technology preview aspect of tree-ssa is the mudflap
bounds-checking work. It demonstrates a tree-rewriting transform that
adds newish functionality, flag-controlled, to the compiler, thus not
becoming a possible performance regression. It could showcase the
value of a generic tree IR, an issue distinct from the presence of
ssa-based optimizations.
- FChE
next prev parent reply other threads:[~2002-12-06 19:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021204102528.75c8b5cc.bkoz@redhat.com>
2002-12-04 8:41 ` [Patch] Qualify min(), max() and distance() in v3 Mark Mitchell
2002-12-04 11:41 ` merging for 3.4 (was Re: [Patch] Qualify min(), max() ...) Diego Novillo
2002-12-04 11:47 ` David Edelsohn
2002-12-04 11:52 ` Gabriel Dos Reis
2002-12-04 11:58 ` David Edelsohn
2002-12-04 12:00 ` Mark Mitchell
2002-12-04 12:21 ` Jan Hubicka
2002-12-06 12:40 ` Frank Ch. Eigler [this message]
2002-12-04 11:49 ` Jan Hubicka
2002-12-04 12:01 ` Diego Novillo
2002-12-04 12:55 ` Joe Buck
2002-12-04 13:08 ` Jan Hubicka
2002-12-04 13:40 ` Neil Booth
[not found] ` <20021204214715.GR5173@kam.mff.cuni.cz>
2002-12-04 13:52 ` Neil Booth
2002-12-04 14:05 ` Toon Moene
2002-12-04 14:00 ` Eric Christopher
2002-12-04 14:08 ` Matt Austern
2002-12-05 12:40 ` compile time regressions (was: merging for 3.4) Gerald Pfeifer
2002-12-05 13:00 ` Jan Hubicka
[not found] ` <200212100246.gBA2kujF029585@gremlin.ics.uci.edu>
2002-12-09 23:26 ` Neil Booth
2002-12-10 6:58 ` Daniel Berlin
[not found] ` <20021210112458.4f4b10ca.bkoz@redhat.com>
2002-12-10 13:39 ` Neil Booth
2002-12-10 14:24 ` Mike Stump
2002-12-10 14:30 ` Neil Booth
2002-12-10 14:40 ` Mike Stump
2002-12-10 15:17 ` Jan Hubicka
2002-12-04 14:23 ` merging for 3.4 (was Re: [Patch] Qualify min(), max() ...) Daniel Berlin
2002-12-04 14:20 ` Daniel Berlin
2002-12-04 11:44 ` [Patch] Qualify min(), max() and distance() in v3 Benjamin Kosnik
2002-12-04 14:25 merging for 3.4 (was Re: [Patch] Qualify min(), max() ...) Robert Dewar
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=o5znrj7x10.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=bkoz@redhat.com \
--cc=dje@watson.ibm.com \
--cc=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=libstdc++@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=pcarlini@unitus.it \
/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).