From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Marek Polacek <polacek@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>,
Jonathan Wakely <jwakely@redhat.com>,
Jason Merrill <jason@redhat.com>
Subject: Re: [PATCH] libstdc++: suppress -Wdangling-reference with operator| [PR111410]
Date: Sat, 20 Jan 2024 07:46:55 +0000 [thread overview]
Message-ID: <CAH6eHdQOnAcf8CPd0zDkLKkWHYMryDCgHWt0GnBCCjLRxc9KBw@mail.gmail.com> (raw)
In-Reply-To: <20240120021751.81798-1-polacek@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2772 bytes --]
On Sat, 20 Jan 2024, 03:47 Marek Polacek, <polacek@redhat.com> wrote:
> Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
>
OK, thanks.
The standard ranges have their own protection against dangling via the
opt-in borrowed_range concept, and algorithms that don't allow returning
iterators into rvalue ranges, and the automatic use of ref_view or
owning_view as needed. So I think it's reasonable to assume they are less
prone to the bugs this warning detects, at least when used idiomatically.
> -- >8 --
> It seems to me that we should exclude
> std::ranges::views::__adaptor::operator|
> from the -Wdangling-reference warning. It's commonly used when handling
> ranges.
>
> PR c++/111410
>
> libstdc++-v3/ChangeLog:
>
> * include/std/ranges: Add #pragma to disable -Wdangling-reference
> with
> std::ranges::views::__adaptor::operator|.
>
> gcc/testsuite/ChangeLog:
>
> * g++.dg/warn/Wdangling-reference17.C: New test.
> ---
> gcc/testsuite/g++.dg/warn/Wdangling-reference17.C | 15 +++++++++++++++
> libstdc++-v3/include/std/ranges | 3 +++
> 2 files changed, 18 insertions(+)
> create mode 100644 gcc/testsuite/g++.dg/warn/Wdangling-reference17.C
>
> diff --git a/gcc/testsuite/g++.dg/warn/Wdangling-reference17.C
> b/gcc/testsuite/g++.dg/warn/Wdangling-reference17.C
> new file mode 100644
> index 00000000000..223698422c2
> --- /dev/null
> +++ b/gcc/testsuite/g++.dg/warn/Wdangling-reference17.C
> @@ -0,0 +1,15 @@
> +// PR c++/111410
> +// { dg-do compile { target c++20 } }
> +// { dg-options "-Wdangling-reference" }
> +
> +#include <vector>
> +#include <ranges>
> +
> +int main()
> +{
> + std::vector v{1, 2, 3, 4, 5};
> + for (auto i : std::span{v} | std::views::take(1))
> + {
> + (void) i;
> + }
> +}
> diff --git a/libstdc++-v3/include/std/ranges
> b/libstdc++-v3/include/std/ranges
> index 7ef835f486a..f2413badd9c 100644
> --- a/libstdc++-v3/include/std/ranges
> +++ b/libstdc++-v3/include/std/ranges
> @@ -942,6 +942,8 @@ namespace views::__adaptor
> concept __is_range_adaptor_closure
> = requires (_Tp __t) {
> __adaptor::__is_range_adaptor_closure_fn(__t, __t); };
>
> +#pragma GCC diagnostic push
> +#pragma GCC diagnostic ignored "-Wdangling-reference"
> // range | adaptor is equivalent to adaptor(range).
> template<typename _Self, typename _Range>
> requires __is_range_adaptor_closure<_Self>
> @@ -961,6 +963,7 @@ namespace views::__adaptor
> return _Pipe<decay_t<_Lhs>,
> decay_t<_Rhs>>{std::forward<_Lhs>(__lhs),
>
> std::forward<_Rhs>(__rhs)};
> }
> +#pragma GCC diagnostic pop
>
> // The base class of every range adaptor non-closure.
> //
>
> base-commit: 615e25c82de97acc17ab438f88d6788cf7ffe1d6
> --
> 2.43.0
>
>
prev parent reply other threads:[~2024-01-20 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 2:17 Marek Polacek
2024-01-20 7:46 ` Jonathan Wakely [this message]
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=CAH6eHdQOnAcf8CPd0zDkLKkWHYMryDCgHWt0GnBCCjLRxc9KBw@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=polacek@redhat.com \
/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).