From: Razya Ladelsky <RAZYA@il.ibm.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org, jh@suse.cz
Subject: Re: IPA branch
Date: Sun, 01 Oct 2006 09:46:00 -0000 [thread overview]
Message-ID: <OFB33D9DF4.66529234-ONC22571FA.00353D97-C22571FA.003573BB@il.ibm.com> (raw)
In-Reply-To: <451C52DC.7050902@codesourcery.com>
Mark Mitchell <mark@codesourcery.com> wrote on 29/09/2006 01:55:24:
> Razya Ladelsky wrote:
>
> > Except for new optimizations, IPCP (currently on mainline) should also
be
> > transformed to SSA.
> > IPCP in SSA code exists on IPA branch, and will be submitted to GCC4.3
> > after IPA branch
> > is committed and some testsuite regressions failing with
> > IPCP+versioning+inlining are fixed.
>
> Is there a project page for this work?
>
No, I haven't put a page for this work yet.
Will do so when I get back on Tuesday.
Just thought it's a part of maintaining IPCP after IPA branch changes.
Thanks,
Razya
> Thanks,
>
> --
> Mark Mitchell
> CodeSourcery
> mark@codesourcery.com
> (650) 331-3385 x713
next prev parent reply other threads:[~2006-10-01 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF6AB9093A.4AE5B747-ONC22571F6.003EE27B-C22571F6.003EEC9B@LocalDomain>
2006-09-27 11:57 ` Razya Ladelsky
2006-09-28 22:57 ` Mark Mitchell
2006-10-01 9:46 ` Razya Ladelsky [this message]
2006-10-05 16:10 ` Razya Ladelsky
2006-09-24 17:21 Mark Mitchell
2006-09-25 13:04 ` Jan Hubicka
2006-09-29 1:52 ` Mark Mitchell
-- strict thread matches above, loose matches on Subject: below --
2005-08-04 16:55 Jan Hubicka
2005-08-04 17:12 ` Jan Hubicka
2005-08-04 18:32 ` Steven Bosscher
2005-08-05 7:35 ` Jan Hubicka
2005-08-05 14:35 ` Gerald Pfeifer
2005-07-20 14:26 Function Inlining for FORTRAN Canqun Yang
2005-07-20 15:24 ` Paul Brook
2005-07-20 15:58 ` Steven Bosscher
2005-07-22 14:11 ` Michael Matz
2005-08-06 1:05 ` IPA branch Canqun Yang
2005-08-06 6:15 ` Andrew Pinski
2005-08-06 8:54 ` Steven Bosscher
2005-08-06 19:20 ` 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=OFB33D9DF4.66529234-ONC22571FA.00353D97-C22571FA.003573BB@il.ibm.com \
--to=razya@il.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=mark@codesourcery.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).