public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Nick Clifton <nickc@sourceware.org>
To: bfd-cvs@sourceware.org, gdb-cvs@sourceware.org
Subject: [binutils-gdb/binutils-2_38-branch] Fix a problem building the libiberty library with gcc-12.
Date: Mon, 24 Jan 2022 18:01:02 +0000 (GMT)	[thread overview]
Message-ID: <20220124180102.C522C3858D3C@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=831970745a7fdccf97648fd566c1a1a56f085e0a

commit 831970745a7fdccf97648fd566c1a1a56f085e0a
Author: Martin Sebor <msebor@redhat.com>
Date:   Mon Jan 24 18:00:17 2022 +0000

    Fix a problem building the libiberty library with gcc-12.
    
            PR 28779
            * regex.c: Suppress -Wuse-after-free.

Diff:
---
 libiberty/ChangeLog | 4 ++++
 libiberty/regex.c   | 4 ++++
 2 files changed, 8 insertions(+)

diff --git a/libiberty/ChangeLog b/libiberty/ChangeLog
index 04c9e90a45b..40611e56ff4 100644
--- a/libiberty/ChangeLog
+++ b/libiberty/ChangeLog
@@ -1,3 +1,7 @@
+2022-01-15  Martin Sebor  <msebor@redhat.com>
+
+	* regex.c: Suppress -Wuse-after-free.
+
 2022-01-22  Nick Clifton  <nickc@redhat.com>
 
 	* 2.38 release branch created.
diff --git a/libiberty/regex.c b/libiberty/regex.c
index cc5a4605ced..84af5276ae8 100644
--- a/libiberty/regex.c
+++ b/libiberty/regex.c
@@ -30,6 +30,10 @@
   #pragma alloca
 #endif
 
+#if __GNUC__ >= 12
+#  pragma GCC diagnostic ignored "-Wuse-after-free"
+#endif
+
 #undef	_GNU_SOURCE
 #define _GNU_SOURCE


                 reply	other threads:[~2022-01-24 18:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220124180102.C522C3858D3C@sourceware.org \
    --to=nickc@sourceware.org \
    --cc=bfd-cvs@sourceware.org \
    --cc=gdb-cvs@sourceware.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).