public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107532] [13 Regression] -Werror=dangling-reference false positives in libcamera-0.0.1
Date: Thu, 23 Mar 2023 13:32:28 +0000	[thread overview]
Message-ID: <bug-107532-4-KNWvqAmyHu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107532-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #27 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:

https://gcc.gnu.org/g:59bfdd5f467292a368d0d628084a4b65d1bb06bb

commit r13-6830-g59bfdd5f467292a368d0d628084a4b65d1bb06bb
Author: Marek Polacek <polacek@redhat.com>
Date:   Fri Mar 17 14:36:10 2023 -0400

    c++: further -Wdangling-reference refinement [PR107532]

    Based on <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107532#c24>,
    it seems like we should treat *any* class with a reference member
    as a reference wrapper.  To suppress the warning in

      int i = 42;
      auto const& v = std::get<0>(std::tuple<int&>(i));

    we have to look into base classes as well.  For std::tuple, this means
    that we have to check the _Head_base subobject, which is a non-direct
    base class of std::tuple.  So I've employed a DFS walk.

            PR c++/107532

    gcc/cp/ChangeLog:

            * call.cc (class_has_reference_member_p): New.
            (class_has_reference_member_p_r): New.
            (reference_like_class_p): Don't look for a specific constructor.
            Use a DFS walk with class_has_reference_member_p_r.

    gcc/testsuite/ChangeLog:

            * g++.dg/warn/Wdangling-reference11.C: New test.
            * g++.dg/warn/Wdangling-reference12.C: New test.

  parent reply	other threads:[~2023-03-23 13:32 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-05  5:48 [Bug c++/107532] New: " slyfox at gcc dot gnu.org
2022-11-05 10:58 ` [Bug c++/107532] " rguenth at gcc dot gnu.org
2022-11-11 20:27 ` mpolacek at gcc dot gnu.org
2022-11-21 10:20 ` marxin at gcc dot gnu.org
2022-12-23  8:28 ` marxin at gcc dot gnu.org
2023-01-13 12:39 ` rguenth at gcc dot gnu.org
2023-01-16 16:43 ` mpolacek at gcc dot gnu.org
2023-01-24 17:38 ` jakub at gcc dot gnu.org
2023-01-24 17:41 ` mpolacek at gcc dot gnu.org
2023-01-24 17:44 ` jakub at gcc dot gnu.org
2023-01-24 17:50 ` mpolacek at gcc dot gnu.org
2023-02-01 14:44 ` pobrn at protonmail dot com
2023-02-14 13:31 ` ecurtin at redhat dot com
2023-02-14 13:45 ` mpolacek at gcc dot gnu.org
2023-03-07 16:11 ` cvs-commit at gcc dot gnu.org
2023-03-07 16:11 ` mpolacek at gcc dot gnu.org
2023-03-08 11:00 ` marxin at gcc dot gnu.org
2023-03-09 11:47 ` marxin at gcc dot gnu.org
2023-03-10 16:46 ` mpolacek at gcc dot gnu.org
2023-03-10 16:52 ` redi at gcc dot gnu.org
2023-03-10 17:02 ` pobrn at protonmail dot com
2023-03-10 17:17 ` mpolacek at gcc dot gnu.org
2023-03-10 17:18 ` mpolacek at gcc dot gnu.org
2023-03-12 10:49 ` eike@sf-mail.de
2023-03-12 13:37 ` flast at flast dot jp
2023-03-13 15:21 ` cvs-commit at gcc dot gnu.org
2023-03-13 15:53 ` mpolacek at gcc dot gnu.org
2023-03-14 23:09 ` flast at flast dot jp
2023-03-16 15:51 ` mpolacek at gcc dot gnu.org
2023-03-16 16:24 ` mpolacek at gcc dot gnu.org
2023-03-23 13:32 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-23 13:33 ` mpolacek at gcc dot gnu.org
2023-03-23 15:22 ` gcc-bugzilla at al42and dot me
2023-04-11 16:09 ` gnu.ojxq8 at dralias dot com
2023-04-12 19:46 ` gnu.ojxq8 at dralias dot com
2023-04-12 19:49 ` mpolacek at gcc dot gnu.org
2023-04-27 22:29 ` cuzdav at gmail dot com
2023-06-12  3:25 ` boris at kolpackov dot net
2023-06-12 16:27 ` mpolacek 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-107532-4-KNWvqAmyHu@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).