This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH 1/9] Change ENABLE_VALGRIND_CHECKING to ENABLE_VALGRIND_ANNOTATIONS guard.

From: Jeff Law <law at redhat dot com>
To: marxin <mliska at suse dot cz>, gcc-patches at gcc dot gnu dot org
Date: Thu, 19 May 2016 12:41:06 -0600
Subject: Re: [PATCH 1/9] Change ENABLE_VALGRIND_CHECKING to ENABLE_VALGRIND_ANNOTATIONS guard.
Authentication-results: sourceware.org; auth=none
References: <cover dot 1463654693 dot git dot mliska at suse dot cz> <f7dd5ae870da3a0ce8cc91e5930968b15a44ca3e dot 1463654693 dot git dot mliska at suse dot cz>

On 05/19/2016 04:43 AM, marxin wrote:

Following change is very similar to what I did in:
https://gcc.gnu.org/ml/gcc-patches/2016-01/msg02103.html

It's more logical to encapsulate valgrind annotation magic within
a ENABLE_VALGRIND_ANNOTATIONS macro rather than ENABLE_VALGRIND_CHECKING.

libcpp/ChangeLog:

2016-05-18  Martin Liska  <mliska@suse.cz>

	* config.in: Regenerated.
	* configure: Likewise.
	* configure.ac: Handle --enable-valgrind-annotations.
	* lex.c (new_buff): Use ENABLE_VALGRIND_ANNOTATIONS instead
	of ENABLE_VALGRIND_CHECKING.
	(_cpp_free_buff): Likewise.

OK.
jeff

References:
- [PATCH 0/9] Remove various memory leaks
  - From: marxin
- [PATCH 1/9] Change ENABLE_VALGRIND_CHECKING to ENABLE_VALGRIND_ANNOTATIONS guard.
  - From: marxin

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]