public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dimitrios Apostolou <jimis@gmx.net>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Paolo Bonzini <bonzini@gnu.org>
Subject: Re: [df-scan.c] Optimise DF_REFs ordering in collection_rec, use HARD_REG_SETs instead of bitmaps
Date: Fri, 08 Jul 2011 07:04:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.02.1107080954490.1237@localhost.localdomain> (raw)
In-Reply-To: <CABu31nPhsfZtMa306WxMg+VmsAjsZKGp2e9237y6OJ6NxzTVzA@mail.gmail.com>

On Fri, 8 Jul 2011, Steven Bosscher wrote:
> On Fri, Jul 8, 2011 at 5:20 AM, Dimitrios Apostolou <jimis@gmx.net> wrote:
>> The attached patch does two things for df_get_call_refs():
>
> How did you test this patch?
>
> Normally, a patch submission comes with text like, "Bootstrapped &
> tested on ..., no regressions.". Also, you chould write a ChangeLog
> entry, best included in your mail somewhere at the end ;-)

Hi Steven, thanks for the instructions. I've not run the mandatory tests 
you have told me about, only done some minor testing due to lack of time. 
I'm not yet posting patches for inclusion, but more as an RFC. Should such 
patches be sent to gcc instead of gcc-patches?


Thanks,
Dimitris

  reply	other threads:[~2011-07-08  6:59 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
2011-07-08  6:37 ` Steven Bosscher
2011-07-08  7:04   ` Dimitrios Apostolou [this message]
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.1107080954490.1237@localhost.localdomain \
    --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).