From: Richard Guenther <richard.guenther@gmail.com>
To: Richard Henderson <rth@redhat.com>
Cc: Ian Lance Taylor <iant@google.com>,
Nick Clifton <nickc@redhat.com>,
gcc-patches@gcc.gnu.org
Subject: Re: Commit: RL78: Include tree-pass.h
Date: Thu, 09 Aug 2012 08:13:00 -0000 [thread overview]
Message-ID: <CAFiYyc0UQwtZcgmUPfL1B8kA0zi+MJkERFYpLv3vpOG=btG2RA@mail.gmail.com> (raw)
In-Reply-To: <502285F4.9040605@redhat.com>
On Wed, Aug 8, 2012 at 5:29 PM, Richard Henderson <rth@redhat.com> wrote:
> On 08/08/2012 07:19 AM, Ian Lance Taylor wrote:
>>> > 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.
>
> I think it makes much more sense to edit the pass ordering from
> the backend, rather than hooks upon hooks upon hooks.
>
> Since the plugin interface exists, we might as well use it.
The issue is that using the plugin interface makes breakage only detectable
when you are able to test a target, not by merely building it. That's bad
(of course only for those weirdo targets). We should _at least_ provide
an interface to internals that for example use the address of the pass
structure for pass placement instead of just the dump file name.
Richard.
>
> r~
next prev parent reply other threads:[~2012-08-09 8:13 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
2012-08-08 15:30 ` Richard Henderson
2012-08-09 8:13 ` Richard Guenther [this message]
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='CAFiYyc0UQwtZcgmUPfL1B8kA0zi+MJkERFYpLv3vpOG=btG2RA@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=nickc@redhat.com \
--cc=rth@redhat.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).