From: Jeff Law <law@redhat.com>
To: Michael Ploujnikov <michael.ploujnikov@oracle.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Jan Hubicka <hubicka@ucw.cz>, Martin Jambor <mjambor@suse.cz>
Subject: Re: [PATCH] Testcase for PR 88297 and minor fixes
Date: Fri, 14 Dec 2018 00:19:00 -0000 [thread overview]
Message-ID: <aa3f4246-8c06-a96e-4d11-0b8dba19968b@redhat.com> (raw)
In-Reply-To: <31ea54fc-3e2e-bfaf-7fa4-5192feb68f52@oracle.com>
On 12/6/18 1:13 PM, Michael Ploujnikov wrote:
> Thanks to Martin we now have a test that exercises (cp) cloning
> machinery during the WPA stage of LTO.
>
> Also, during debugging I found that print_all_lattices would trigger
> an assert if I tried to call it inside decide_whether_version_node.
>
> Finally I've attached some comment spelling fixes as a bonus.
>
>
> Bootstrapping (--with-build-config=bootstrap-lto) and regression testing on x86_64.
>
> Ok for trunk after tests pass?
Thanks. I went ahead and installed all 3 patches on the trunk.
jeff
prev parent reply other threads:[~2018-12-14 0:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 20:13 Michael Ploujnikov
2018-12-12 18:01 ` [PING 1] " Michael Ploujnikov
2018-12-14 0:19 ` Jeff Law [this message]
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=aa3f4246-8c06-a96e-4d11-0b8dba19968b@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=michael.ploujnikov@oracle.com \
--cc=mjambor@suse.cz \
/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).