public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: Nick Clifton <nickc@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: Commit: RL78: Include tree-pass.h
Date: Wed, 08 Aug 2012 14:19:00 -0000	[thread overview]
Message-ID: <CAKOQZ8xdD_mYtwLkTH0+=6u3j4OYDCMues4zdJ3ph71bfSyU5A@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc1JZnYOOTwF5F2ubGb0er3x3gG9de7u0fn+MhFin1KQvg@mail.gmail.com>

On Wed, Aug 8, 2012 at 7:11 AM, Richard Guenther
<richard.guenther@gmail.com> wrote:
> On Wed, Aug 8, 2012 at 4:06 PM, Ian Lance Taylor <iant@google.com> wrote:
>> On Wed, Aug 8, 2012 at 7:03 AM, Richard Guenther
>> <richard.guenther@gmail.com> wrote:
>>
>>> I don't think we really want that (machine dependent passes).  It seems
>>> we cannot get away with it (so we have mdreorg).  Allowing (some) flexibility
>>> where to put mdreorg is ok, using two different mechanisms (mdreorg and
>>> a "plugin") sounds odd and is IMHO bad for consistency.
>>
>> I think we definitely want machine dependent passes.  E.g., reg-stack
>> should be one.  The passes should live by normal rules, they shouldn't
>> be like mdreorg.
>
> What is "like mdreorg"?  That it is a pass centrally registered,
> called "mdreorg"
> that calls a target hook which happens to implement the pass?  regstack
> is controlled by a target macro and is centrally registered, too.
>
>> I don't really care about the mechanism as long as it exists.
>
> I was suggesting to for example register a 2nd mdreorg-like pass and
> add a 2nd target hook.  regstack should get the same treatment.

If the mechanism is a proliferation of mdreorg passes in every place
we want a target-specific pass, that is fine with me.

Ian

  reply	other threads:[~2012-08-08 14:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08  8:34 Nick Clifton
2012-08-08  8:45 ` Richard Guenther
2012-08-08  9:08   ` nick clifton
2012-08-08  9:22     ` Richard Guenther
2012-08-08 13:36   ` Ian Lance Taylor
2012-08-08 14:03     ` Richard Guenther
2012-08-08 14:06       ` Ian Lance Taylor
2012-08-08 14:12         ` Richard Guenther
2012-08-08 14:19           ` Ian Lance Taylor [this message]
2012-08-08 15:30             ` Richard Henderson
2012-08-09  8:13               ` Richard Guenther
2012-08-09 16:45                 ` DJ Delorie
2012-08-08 15:38     ` DJ Delorie
2012-08-08 17:52       ` Beyond Complex Register Management Mike Stump
2012-08-08 18:14         ` DJ Delorie
2012-08-08 22:29           ` Mike Stump
2012-08-08 18:18         ` Nathan Froyd
2012-08-08 22:01           ` Mike Stump

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='CAKOQZ8xdD_mYtwLkTH0+=6u3j4OYDCMues4zdJ3ph71bfSyU5A@mail.gmail.com' \
    --to=iant@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nickc@redhat.com \
    --cc=richard.guenther@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).