From: Ian Lance Taylor <iant@google.com>
To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
Cc: anemet@caviumnetworks.com, gcc-patches@gcc.gnu.org,
richard@codesourcery.com, sandra@codesourcery.com
Subject: Re: [PATCH, MIPS] Fix build after no_new_pseudos
Date: Mon, 16 Jul 2007 17:33:00 -0000 [thread overview]
Message-ID: <m3d4ys9s7a.fsf@localhost.localdomain> (raw)
In-Reply-To: <10707161721.AA21942@vlsi1.ultra.nyu.edu>
kenner@vlsi1.ultra.nyu.edu (Richard Kenner) writes:
> > I think we should fix combine to permit splitters to create new
> > pseudos. I don't think it does us any useful service to prohibit
> > them.
>
> What if the splitter doesn't result in a recognized insn (most don't).
> We could potentially be creating a lot of unneeded pseudos.
I'm not sure I agree. I suspect that most splitters, when they
succeed, do result in recognized insns.
Conversely, some splitters may require a new pseudo, and yet be quite
useful if they can be run during combine.
In any case, this is something we can measure.
Ian
next prev parent reply other threads:[~2007-07-16 17:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 19:16 Adam Nemet
2007-07-16 9:43 ` Richard Sandiford
2007-07-16 16:50 ` Ian Lance Taylor
2007-07-16 17:26 ` Richard Kenner
2007-07-16 17:33 ` Ian Lance Taylor [this message]
2007-07-16 18:12 ` Adam Nemet
2007-07-24 2:22 ` Sandra Loosemore
2007-07-24 16:41 ` Adam Nemet
2007-07-26 4:20 ` Ian Lance Taylor
2007-07-18 12:08 ` Richard Sandiford
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=m3d4ys9s7a.fsf@localhost.localdomain \
--to=iant@google.com \
--cc=anemet@caviumnetworks.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
--cc=richard@codesourcery.com \
--cc=sandra@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).