public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Sandiford <richard.sandiford@linaro.org>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,  Jie Zhang <jzhang918@gmail.com>
Subject: Re: Generic hwloop support library
Date: Fri, 08 Jul 2011 08:40:00 -0000	[thread overview]
Message-ID: <g4k4btgobl.fsf@linaro.org> (raw)
In-Reply-To: <4E15D455.5090709@codesourcery.com> (Bernd Schmidt's message of	"Thu, 07 Jul 2011 17:44:21 +0200")

Bernd Schmidt <bernds@codesourcery.com> writes:
> On 07/05/11 21:25, Richard Sandiford wrote:
>> A C bootstrap only should be fine of course, since the code isn't
>> going to be run.)
>> 
>>> +  hwloop_info loops = NULL;
>> 
>> Unnecessary initialisation (or at least, it should be).
>
> ? The value is used inside the loop to initialize "next" of the first loop.

Sorry, I probably cut too much context.  I meant the initialisation here:

+  hwloop_info loops = NULL;
+  hwloop_info loop;
+  bitmap_obstack stack;
+
+  df_live_add_problem ();
+  df_live_set_all_dirty ();
+  df_analyze ();
+
+  bitmap_obstack_initialize (&stack);
+
+  if (dump_file)
+    fprintf (dump_file, ";; Find loops, first pass\n\n");
+
+  loops = discover_loops (&stack, hooks);

Richard

  reply	other threads:[~2011-07-08  8:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 13:55 Bernd Schmidt
2011-07-02 13:03 ` Richard Sandiford
2011-07-04 22:31   ` Bernd Schmidt
2011-07-05 19:36     ` Richard Sandiford
2011-07-07 15:47       ` Bernd Schmidt
2011-07-08  8:40         ` Richard Sandiford [this message]
2011-07-03 13:59 ` Steven Bosscher

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=g4k4btgobl.fsf@linaro.org \
    --to=richard.sandiford@linaro.org \
    --cc=bernds@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jzhang918@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).