public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r12-7204] libstdc++: Fix FAIL: 20_util/temporary_buffer.cc for C++14
Date: Fri, 11 Feb 2022 22:15:11 +0000 (GMT)	[thread overview]
Message-ID: <20220211221511.6675F385800A@sourceware.org> (raw)

https://gcc.gnu.org/g:9a56779dbc4e2d9c15be8d31e36f2f59be7331a8

commit r12-7204-g9a56779dbc4e2d9c15be8d31e36f2f59be7331a8
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Feb 10 17:34:58 2022 +0000

    libstdc++: Fix FAIL: 20_util/temporary_buffer.cc for C++14
    
    The std::get_temporary_buffer function is deprecated since C++17, but
    the test was expecting a warning for C++14 as well.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/20_util/temporary_buffer.cc: Fix dg-warning target
            selector.

Diff:
---
 libstdc++-v3/testsuite/20_util/temporary_buffer.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/20_util/temporary_buffer.cc b/libstdc++-v3/testsuite/20_util/temporary_buffer.cc
index 3f3625961b6..54b0edb00ee 100644
--- a/libstdc++-v3/testsuite/20_util/temporary_buffer.cc
+++ b/libstdc++-v3/testsuite/20_util/temporary_buffer.cc
@@ -27,7 +27,7 @@ struct junk { char j[12]; };
 int main(void)
 {
   typedef std::pair<junk*, std::ptrdiff_t> pair_type;
-  pair_type results = std::get_temporary_buffer<junk>(5); // { dg-warning "deprecated" "" { target c++14 } }
+  pair_type results = std::get_temporary_buffer<junk>(5); // { dg-warning "deprecated" "" { target c++17 } }
 
   if (results.second != 0)
   {


                 reply	other threads:[~2022-02-11 22:15 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=20220211221511.6675F385800A@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).