public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dimitrios Apostolou <jimis@gmx.net>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: gcc-patches@gcc.gnu.org, Steven Bosscher <stevenb.gcc@gmail.com>
Subject: Re: [df-scan.c] Optimise DF_REFs ordering in collection_rec, use HARD_REG_SETs instead of bitmaps
Date: Sat, 09 Jul 2011 01:29:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.02.1107090334130.1581@beee> (raw)
In-Reply-To: <4E16ABD2.2050701@gnu.org>

On Fri, 8 Jul 2011, Paolo Bonzini wrote:
> On 07/08/2011 05:51 AM, Dimitrios Apostolou wrote:
>> +	  /* first write DF_REF_BASE */
>
> This is not necessary.  These uses are written to use_vec, while the uses 
> from REG_EQUIV and REG_EQUAL are written to eq_use_vec (see 
> df_ref_create_structure).

Thanks for pointing this out, I missed it, it's complex to follow 
what is written where. Perhaps there is meaning in changing the interface 
of df_ref_create_structure() to accept the particular vector.

>
> Also, anyway this wouldn't work because you would have to split the loop in 
> two.  I'll attribute that to the time of day when you were writing the 
> message. :)

Even though I'm having my own disputes with Morpheus, sleep deprivation 
wasn't tha culprit for this. :-) My intention was to keep DF_REF_BASEs as 
close to each other, because a close-to-be-sorted array will be sorted 
faster with the sorting function I'll write... :-)

But anyway as you've explained it's irrelevant since they are going 
to different vectors.


Thanks,
Dimitris

  reply	other threads:[~2011-07-09  1:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-08  3:33 Dimitrios Apostolou
2011-07-08  3:52 ` Dimitrios Apostolou
2011-07-08  6:36 ` Dimitrios Apostolou
2011-07-08  7:12   ` Paolo Bonzini
2011-07-09  1:29     ` Dimitrios Apostolou [this message]
2011-07-08  6:37 ` Steven Bosscher
2011-07-08  7:04   ` Dimitrios Apostolou
2011-07-08  6:59 ` Jakub Jelinek
2011-07-08  9:09   ` Dimitrios Apostolou
2011-07-08 14:22     ` Paolo Bonzini
2011-07-08 14:25       ` Paolo Bonzini
2011-07-08  8:42 ` Richard Guenther
2011-07-08 10:20   ` Dimitrios Apostolou

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.LNX.2.02.1107090334130.1581@beee \
    --to=jimis@gmx.net \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=stevenb.gcc@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).