From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-420175-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 129470 invoked by alias); 27 Jan 2016 13:04:56 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 129456 invoked by uid 89); 27 Jan 2016 13:04:55 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=
X-HELO: mail-yk0-f172.google.com
Received: from mail-yk0-f172.google.com (HELO mail-yk0-f172.google.com) (209.85.160.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Wed, 27 Jan 2016 13:04:54 +0000
Received: by mail-yk0-f172.google.com with SMTP id k129so8701351yke.0        for <gcc-patches@gcc.gnu.org>; Wed, 27 Jan 2016 05:04:54 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:mime-version:in-reply-to:references:date         :message-id:subject:from:to:cc:content-type         :content-transfer-encoding;        bh=FkG/54HFo3tpWYSoTDReHA67CfOChauGUOX+gmSMYFY=;        b=N3+GlCoVyIOaD+Fap8hQ79OPtouUWih8nY0tFyf12ww0sHoGZRSSan0XMhx5QtfIkI         5h1+QH5bW0Lh458DdRB6LRL8rf0a9nwkyqnBrVQgBlbmBosYd0LengoJDf4O1eQarPan         hliyru+UKqBMjxIf3/w5ZCnCWP+grG+UhZedsh+RCvlKxkGWzHeKLm4kqMCwiBO2IfEt         lGvYomyDZmEPwmAK2PvdtWEPXp8XWbqv/6hiOwVwzW/GLiEJYvv3124ApegDJ3lYYHdf         jotRz9gt7V0wyDTOxS0ObbIaTROrMmh99lKEEj+MESAxWIxgTx7LuR9XhXt9vrMp2uM1         QbiA==
X-Gm-Message-State: AG10YOQeuBvvVHKipDcQG/wJ4u0tf+ORiXZ+aup4b2rnx0XvbSX2pWqPRjxJTVj3DPBCDJVbGoqJpmBfe/oJ3w==
MIME-Version: 1.0
X-Received: by 10.37.18.139 with SMTP id 133mr14392069ybs.169.1453899892382; Wed, 27 Jan 2016 05:04:52 -0800 (PST)
Received: by 10.37.202.82 with HTTP; Wed, 27 Jan 2016 05:04:52 -0800 (PST)
In-Reply-To: <56A8BD81.2040000@suse.cz>
References: <56A8BD81.2040000@suse.cz>
Date: Wed, 27 Jan 2016 13:04:00 -0000
Message-ID: <CAFiYyc0XWTJJ8fGacQcuwh6q+FOMn4rJpgzOA-ABVm_o9Rz=6Q@mail.gmail.com>
Subject: Re: [PATCH] Fix PR pch/68758
From: Richard Biener <richard.guenther@gmail.com>
To: =?UTF-8?Q?Martin_Li=C5=A1ka?= <mliska@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Jakub Jelinek <jakub@redhat.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
X-SW-Source: 2016-01/txt/msg02105.txt.bz2

On Wed, Jan 27, 2016 at 1:52 PM, Martin Li=C5=A1ka <mliska@suse.cz> wrote:
> Hello.
>
> As mentioned in: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D68758#c5,=
 I consider
> more logic to encapsulate valgrind annotation magic within a ENABLE_VALGR=
IND_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