public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@bitrange.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [committed] libstdc++: Fix test failures at -O0
Date: Sun, 13 Feb 2022 16:20:18 -0500 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.20.16.2202131614530.10262@arjuna.pair.com> (raw)
In-Reply-To: <20220211221551.3383447-1-jwakely@redhat.com>

On Fri, 11 Feb 2022, Jonathan Wakely via Gcc-patches wrote:
> diff --git a/libstdc++-v3/testsuite/20_util/unsynchronized_pool_resource/allocate.cc b/libstdc++-v3/testsuite/20_util/unsynchronized_pool_resource/allocate.cc
> index c81344a20e4..25e5ce63b58 100644
> --- a/libstdc++-v3/testsuite/20_util/unsynchronized_pool_resource/allocate.cc
> +++ b/libstdc++-v3/testsuite/20_util/unsynchronized_pool_resource/allocate.cc
> @@ -281,10 +281,13 @@ test07()
>    std::pmr::unsynchronized_pool_resource upr(&cr);
>    try
>    {
> +#pragma GCC diagnostic push
> +#pragma GCC diagnostic ignored "-Walloc-size-larger-than="
>      // Try to allocate a ridiculous size (and use a large extended alignment
>      // so that careful_resource::do_allocate can distinguish this allocation
>      // from any required for the pool resource's internal data structures):
>      void* p = upr.allocate(std::size_t(-2), 1024);
> +#pragma GCC distinguish pop

Isn't it a bug that you (presumably) didn't get an error for
that misspelling?  Or a diagnostic to distinguish it?  8-}

brgds, H-P

  reply	other threads:[~2022-02-13 21:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 22:15 Jonathan Wakely
2022-02-13 21:20 ` Hans-Peter Nilsson [this message]
2022-02-13 22:15   ` Jonathan Wakely

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=alpine.BSF.2.20.16.2202131614530.10262@arjuna.pair.com \
    --to=hp@bitrange.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@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).