public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexander Monakov <amonakov@ispras.ru>
To: gcc-patches@gcc.gnu.org
Cc: Alexander Monakov <amonakov@ispras.ru>
Subject: [PATCH 0/2] Clean up Valgrind configury
Date: Thu, 23 Nov 2023 21:13:41 +0300	[thread overview]
Message-ID: <20231123181343.27624-1-amonakov@ispras.ru> (raw)

We have an RFC patch [1] that adds a libgcc wrapper for a Valgrind client
request.  GCC has autoconf detection for Valgrind in the compiler proper
as well as libcpp (where it is actually unnecessary).

It's grown rusty, let's clean it up.

[1] https://inbox.sourceware.org/gcc-patches/20231024141124.210708-1-exactlywb@ispras.ru/

Alexander Monakov (2):
  libcpp: configure: drop unused Valgrind detection
  gcc: configure: drop Valgrind 3.1 compatibility

 gcc/config.in       | 12 -------
 gcc/configure       | 80 +++++++--------------------------------------
 gcc/configure.ac    | 49 +++------------------------
 gcc/system.h        | 23 ++-----------
 libcpp/config.in    | 15 ++-------
 libcpp/configure    | 70 +--------------------------------------
 libcpp/configure.ac | 51 ++---------------------------
 libcpp/lex.cc       |  4 +--
 8 files changed, 29 insertions(+), 275 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-11-23 18:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23 18:13 Alexander Monakov [this message]
2023-11-23 18:13 ` [PATCH 1/2] libcpp: configure: drop unused Valgrind detection Alexander Monakov
2023-11-24  8:10   ` Richard Biener
2023-11-23 18:13 ` [PATCH 2/2] gcc: configure: drop Valgrind 3.1 compatibility Alexander Monakov
2023-11-24  8:10   ` Richard Biener

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=20231123181343.27624-1-amonakov@ispras.ru \
    --to=amonakov@ispras.ru \
    --cc=gcc-patches@gcc.gnu.org \
    /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).