From: Richard Biener <richard.guenther@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix PR ipa/68035 (v2)
Date: Thu, 12 Nov 2015 11:23:00 -0000 [thread overview]
Message-ID: <CAFiYyc37xOVBp6Q-ZUQfu9n4Z6FP3ZxO37b7oJa5-y_TfVXf5g@mail.gmail.com> (raw)
In-Reply-To: <5644606F.6000801@suse.cz>
On Thu, Nov 12, 2015 at 10:48 AM, Martin Liška <mliska@suse.cz> wrote:
> Hello.
>
> I'm sending reworked version of the patch, where I renamed 'sem_item::hash' to 'm_hash'
> and wrapped all usages with 'get_hash'. Apart from that, a new member function 'set_hash'
> is utilized for changing the hash value. Hope it's easier for understanding.
>
> Patch can survive regression tests and bootstraps on x86_64-linux-pc.
>
> Ready for trunk?
Ok.
Thanks,
Richard.
> Thanks,
> Martin
prev parent reply other threads:[~2015-11-12 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 9:10 [PATCH] Fix PR ipa/68035 Martin Liška
2015-11-06 13:13 ` Richard Biener
2015-11-06 16:44 ` Jan Hubicka
2015-11-12 9:50 ` Martin Liška
2015-11-12 18:40 ` Jan Hubicka
2015-11-13 12:07 ` Martin Liška
2015-11-12 9:48 ` [PATCH] Fix PR ipa/68035 (v2) Martin Liška
2015-11-12 11:23 ` Richard Biener [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=CAFiYyc37xOVBp6Q-ZUQfu9n4Z6FP3ZxO37b7oJa5-y_TfVXf5g@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mliska@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).