From: Trevor Saunders <tbsaunde@tbsaunde.org>
To: Mikhail Maltsev <maltsevm@gmail.com>
Cc: gcc-patches <gcc-patches@gnu.org>, Jeff Law <law@redhat.com>
Subject: Re: [PATCH, RFC]: Next stage1, refactoring: propagating rtx subclasses
Date: Sat, 09 May 2015 05:49:00 -0000 [thread overview]
Message-ID: <20150509054910.GA29362@tsaunders-iceball.corp.tor1.mozilla.com> (raw)
In-Reply-To: <5547D766.5090806@gmail.com>
On Mon, May 04, 2015 at 11:32:38PM +0300, Mikhail Maltsev wrote:
> > You'd probably be better off creating a unique rtx_insn * object and
> > using that as the marker.
> OK. Fixed the patch. Rebased and tested on x86_64-linux (fortunately, it
> did not conflict with Trevor's series of rtx_insn-related patches).
ok, that second series is now in. I think you might conflict with the
last patch, but I think your patch is a super set of what I did so the
rebase should still be simple.
Trev
next prev parent reply other threads:[~2015-05-09 5:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 4:38 Mikhail Maltsev
2015-03-31 15:52 ` Trevor Saunders
2015-04-02 21:13 ` Jeff Law
2015-04-25 11:49 ` Richard Sandiford
2015-04-27 16:38 ` Jeff Law
2015-04-27 16:57 ` Richard Sandiford
2015-04-27 20:01 ` Mikhail Maltsev
2015-04-28 13:50 ` Richard Sandiford
2015-04-28 17:12 ` Jeff Law
2015-04-29 8:02 ` Mikhail Maltsev
2015-04-30 3:54 ` Jeff Law
2015-04-30 5:46 ` Jeff Law
2015-05-04 20:32 ` Mikhail Maltsev
2015-05-04 21:22 ` Trevor Saunders
2015-05-09 5:49 ` Trevor Saunders [this message]
[not found] ` <5547D40F.6010802@gmail.com>
2015-05-08 21:54 ` Jeff Law
2015-05-11 20:41 ` Mikhail Maltsev
2015-05-11 21:21 ` Joseph Myers
2015-05-12 20:26 ` Jeff Law
2015-06-06 5:51 ` Mikhail Maltsev
2015-04-28 23:55 ` Jeff Law
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=20150509054910.GA29362@tsaunders-iceball.corp.tor1.mozilla.com \
--to=tbsaunde@tbsaunde.org \
--cc=gcc-patches@gnu.org \
--cc=law@redhat.com \
--cc=maltsevm@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).