public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, richard.sandiford@arm.com
Subject: Re: Extend tree-call-cdce to calls whose result is used
Date: Mon, 16 Nov 2015 16:19:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.20.1511161711470.11029@wotan.suse.de> (raw)
In-Reply-To: <CAFiYyc1N6WAPj1KnxpRXjd55Y-VgQ8xtfM2qiK-9rxFK8gOC5Q@mail.gmail.com>

Hi,

On Mon, 16 Nov 2015, Richard Biener wrote:

> >> Which would leave us with a lowering stage early in the main 
> >> optimization pipeline - I think fold_builtins pass is way too late 
> >> but any "folding" pass will do (like forwprop or backprop where the 
> >> latter might be better because it might end up computing FP "ranges" 
> >> to improve the initial lowering code).
> >
> > This isn't at all related to what backprop is doing though. backprop 
> > is about optimising definitions based on information about all uses.

Right, I think backprop would be even worse than call_cdce, that pass has 
a completely different structure.

> >> Of course call_cdce is as good as long as it still exists.
> >
> > Does this meann that you're not against the patch in principle (i.e. 
> > keeping call_cdce for now and extending it in the way that this patch 
> > does)?
> 
> Yes, I'm fine with extending call_cdce.  Of course I'd happily approve a 
> patch dissolving it into somewhere where it makes more sense.  But this 
> shouldn't block this patch.

Okay, I like merging passes, so I'll try to do that, once the stuff is in 
:)


Ciao,
Michael.

  reply	other threads:[~2015-11-16 16:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07 13:33 Richard Sandiford
2015-11-09 14:30 ` Michael Matz
2015-11-09 15:18   ` Richard Sandiford
2015-11-09 17:02     ` Michael Matz
2015-11-09 18:02       ` Richard Sandiford
2015-11-09 21:03         ` Michael Matz
2015-11-10 10:02           ` Richard Biener
2015-11-13 13:12             ` Richard Sandiford
2015-11-16 14:01               ` Richard Biener
2015-11-16 16:19                 ` Michael Matz [this message]
2015-11-17  9:20                 ` Richard Sandiford
2015-11-17 14:26                   ` Richard Biener
2015-11-09 23:49 ` Joseph Myers

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=alpine.LSU.2.20.1511161711470.11029@wotan.suse.de \
    --to=matz@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    --cc=richard.sandiford@arm.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).