public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "miro.palmu at helsinki dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109642] False Positive -Wdangling-reference with std::span-like classes
Date: Wed, 17 Jan 2024 12:16:03 +0000	[thread overview]
Message-ID: <bug-109642-4-GQVjwr5XV2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109642-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109642

Miro Palmu <miro.palmu at helsinki dot fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |miro.palmu at helsinki dot fi

--- Comment #11 from Miro Palmu <miro.palmu at helsinki dot fi> ---
I'm not sure if this is useful information but, using span with a view in a
ranged-based for loop triggers false positive -Wdangling-referene on gcc 14.0.1
20240117 but not on gcc 13.2.

// On godbold: https://godbolt.org/z/x9jKh4MoW
#include <ranges>
#include <vector>
#include <span>

int main() {
    const auto vec = std::vector{ 1, 2, 3 };
    const auto s = std::span<decltype(vec)::value_type const>{vec};

    // -Wwaring=dangling-reference on gcc 14.0.1 20240117 but not on gcc 13.2
    for ([[maybe_unused]] auto _ : s | std::views::take(2)) { }

    // No warning
    for ([[maybe_unused]] auto _ : vec | std::views::take(2)) { }

    // No warning
    const auto s_view = s | std::views::take(2);
    for ([[maybe_unused]] auto _ : s_view) { }
}

  parent reply	other threads:[~2024-01-17 12:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-27  6:36 [Bug c++/109642] New: " carlosgalvezp at gmail dot com
2023-04-27  7:03 ` [Bug c++/109642] " pinskia at gcc dot gnu.org
2023-04-27  7:09 ` carlosgalvezp at gmail dot com
2023-04-27 15:49 ` mpolacek at gcc dot gnu.org
2023-04-27 19:20 ` carlosgalvezp at gmail dot com
2023-04-28 13:00 ` mpolacek at gcc dot gnu.org
2023-04-28 14:08 ` carlosgalvezp at gmail dot com
2023-05-02 19:49 ` cvs-commit at gcc dot gnu.org
2023-06-21 18:43 ` pinskia at gcc dot gnu.org
2023-06-21 18:51 ` mpolacek at gcc dot gnu.org
2023-06-21 19:06 ` barry.revzin at gmail dot com
2024-01-17 12:16 ` miro.palmu at helsinki dot fi [this message]
2024-01-19 17:35 ` mpolacek at gcc dot gnu.org
2024-01-19 23:32 ` mpolacek at gcc dot gnu.org
2024-01-22 20:52 ` mpolacek at gcc dot gnu.org
2024-01-22 21:16 ` cvs-commit at gcc dot gnu.org
2024-01-30 18:32 ` mpolacek at gcc dot gnu.org
2024-01-30 18:38 ` lopresti at gmail dot com
2024-01-30 18:42 ` mpolacek at gcc dot gnu.org
2024-03-01 20:55 ` cvs-commit at gcc dot gnu.org
2024-05-01 17:18 ` pinskia at gcc dot gnu.org

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=bug-109642-4-GQVjwr5XV2@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).