public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] Fix PR pch/68758
Date: Wed, 27 Jan 2016 13:04:00 -0000	[thread overview]
Message-ID: <CAFiYyc0XWTJJ8fGacQcuwh6q+FOMn4rJpgzOA-ABVm_o9Rz=6Q@mail.gmail.com> (raw)
In-Reply-To: <56A8BD81.2040000@suse.cz>

On Wed, Jan 27, 2016 at 1:52 PM, Martin Liška <mliska@suse.cz> wrote:
> Hello.
>
> As mentioned in: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68758#c5, I consider
> more logic to encapsulate valgrind annotation magic within a ENABLE_VALGRIND_ANNOTATIONS
> macro rather than ENABLE_VALGRIND_CHECKING.
>
> With patch applied, ggc invalid reads/writes, reported by valgrind tool, are gone.
> The patch can survive regression tests and bootstrap on x86_64-linux-gnu?
>
> Ready for trunk?

Ok.

THanks,
RIchard.

> Thanks,
> Martin

      reply	other threads:[~2016-01-27 13:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 12:52 Martin Liška
2016-01-27 13:04 ` 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='CAFiYyc0XWTJJ8fGacQcuwh6q+FOMn4rJpgzOA-ABVm_o9Rz=6Q@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --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).