From: Jeff Law <law@redhat.com>
To: Nikolai Bozhenov <n.bozhenov@samsung.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Cc: maltsevm@gmail.com
Subject: Re: Fix prototype for print_insn in rtl.h
Date: Tue, 13 Oct 2015 12:22:00 -0000 [thread overview]
Message-ID: <561CF795.8010502@redhat.com> (raw)
In-Reply-To: <561CBEF8.3040300@samsung.com>
On 10/13/2015 02:21 AM, Nikolai Bozhenov wrote:
> Currently prototype for print_insn in rtl.h doesn't match it's
> definition in sched-vis.c The patch fixes this mismatch.
I'll run this through the usual bootstrap & regression testing before
installing later today.
jeff
next prev parent reply other threads:[~2015-10-13 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 8:21 Nikolai Bozhenov
2015-10-13 12:22 ` Jeff Law [this message]
2015-10-13 12:41 ` Nikolai Bozhenov
2015-10-13 13:02 ` Jeff Law
2015-10-13 15:32 ` Jeff Law
2015-10-15 16:28 ` Andrew MacLeod
2015-10-15 16:48 ` Nikolai Bozhenov
2015-10-15 18:43 ` Trevor Saunders
2015-10-20 7:35 ` Nikolai Bozhenov
2015-10-21 6:08 ` [PATCH] Move RTL printing code from sched-vis.c into print-rtl.c Jeff Law
2015-10-19 15:17 ` Fix prototype for print_insn in rtl.h Jeff Law
2015-10-19 16:43 ` 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=561CF795.8010502@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=maltsevm@gmail.com \
--cc=n.bozhenov@samsung.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).