public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: Paolo Bonzini <bonzini@gnu.org>,
	Bernd Schmidt <bernds@codesourcery.com>,
	       GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: New optimization for reload_combine
Date: Mon, 19 Jul 2010 16:13:00 -0000	[thread overview]
Message-ID: <4C447985.4010606@redhat.com> (raw)
In-Reply-To: <4C44791A.8050406@codesourcery.com>

On 07/19/10 10:11, Mark Mitchell wrote:
> Paolo Bonzini wrote:
>
>    
>>> Does postreload.c fall under reload?  If not, would someone approve this?
>>>        
>> Well, it was part of reload1.c until a while ago...
>>      
> Without commenting on the patch (which Jeff has already reviewed), I
> think that postreload should fall in the scope of "reload maintainer".
> Does anyone object?
>    
Nope.  Sounds quite reasonable to me.

jeff

  reply	other threads:[~2010-07-19 16:13 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-16 10:35 Bernd Schmidt
2010-07-16 18:32 ` Jeff Law
2010-07-16 23:50   ` Bernd Schmidt
2010-07-17  2:38     ` H.J. Lu
2010-07-17 14:25       ` Bernd Schmidt
2010-07-17 15:03         ` H.J. Lu
2010-07-17 15:10           ` IainS
2010-07-17 16:00           ` Bernd Schmidt
2010-07-17 16:15             ` H.J. Lu
2010-07-17 17:18               ` Bernd Schmidt
2010-07-17 17:27                 ` H.J. Lu
2010-07-17 17:29                 ` IainS
2010-07-18 18:15             ` H.J. Lu
2010-07-19 10:01           ` Bernd Schmidt
2010-07-19 13:27             ` H.J. Lu
2010-07-20 11:46             ` Bernd Schmidt
2010-07-20 15:33               ` Jeff Law
2010-07-20 15:34               ` Bernd Schmidt
2010-07-20 15:40                 ` Jakub Jelinek
2010-07-19 15:41         ` x86_64 varargs setup jump table Richard Henderson
2010-07-19 15:56           ` H.J. Lu
2010-07-19 20:57             ` H.J. Lu
2010-07-19 21:14               ` Richard Henderson
2010-07-20 16:32                 ` Richard Henderson
2010-07-20 23:05                   ` Richard Henderson
2010-07-20 23:21                     ` Sebastian Pop
2010-07-22 13:52                     ` H.J. Lu
2010-07-22 18:03                       ` Sebastian Pop
2010-07-22 18:15                         ` Richard Henderson
2010-07-22 18:17                           ` Richard Henderson
2010-07-22 18:20                             ` Sebastian Pop
2010-07-21 23:15                   ` H.J. Lu
2010-07-22 21:53                     ` Fix target/45027 [was: x86_64 varargs setup jump table] Richard Henderson
2010-07-23  9:07                       ` Richard Guenther
2010-07-19 16:09           ` x86_64 varargs setup jump table Andi Kleen
2010-07-19 16:16             ` H.J. Lu
2010-07-19 16:26               ` Andi Kleen
2010-07-19 16:23           ` Jan Hubicka
2010-07-19 16:19         ` New optimization for reload_combine Jeff Law
2010-11-04  4:30       ` H.J. Lu
2010-07-16 19:45 ` Paolo Bonzini
2010-07-16 19:55   ` Bernd Schmidt
2010-07-16 20:24     ` Paolo Bonzini
2010-07-19 16:11   ` Mark Mitchell
2010-07-19 16:13     ` Jeff Law [this message]
2010-07-19 16:31     ` Paolo Bonzini
2010-07-26 10:13 ` IainS
2010-07-26 10:46   ` Bernd Schmidt
2010-07-27  0:53   ` Bernd Schmidt

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=4C447985.4010606@redhat.com \
    --to=law@redhat.com \
    --cc=bernds@codesourcery.com \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mark@codesourcery.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).