From: Bernd Schmidt <bschmidt@redhat.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
Kelvin Nilsen <kdnilsen@linux.vnet.ibm.com>,
gcc-patches@gcc.gnu.org
Subject: Re: RFC: Incomplete Draft Patches to Correct Errors in Loop Unrolling Frequencies (bugzilla problem 68212)
Date: Tue, 10 Nov 2015 10:16:00 -0000 [thread overview]
Message-ID: <5641C3EF.9090300@redhat.com> (raw)
In-Reply-To: <4464BBD5-FAF8-4E47-876A-995AB9B85224@gmail.com>
On 11/10/2015 10:56 AM, Bernhard Reutner-Fischer wrote:
> On November 9, 2015 6:35:20 PM GMT+01:00, Bernd Schmidt <bschmidt@redhat.com> wrote:
>> I think something that starts with bb->loop_father and iterates
>> outwards
>> would be more efficient.
>
> flow_bb_inside_loop_p() ?
Ah thanks. I knew there must be one but I couldn't find it.
Bernd
next prev parent reply other threads:[~2015-11-10 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 14:45 Kelvin Nilsen
2015-11-09 17:35 ` Bernd Schmidt
2015-11-10 9:56 ` Bernhard Reutner-Fischer
2015-11-10 10:16 ` Bernd Schmidt [this message]
2015-11-10 10:54 ` Richard Biener
2015-11-10 14:19 ` Michael Matz
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=5641C3EF.9090300@redhat.com \
--to=bschmidt@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kdnilsen@linux.vnet.ibm.com \
--cc=rep.dot.nop@gmail.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).