public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "thiago at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104492] New: Bogus dangling pointer warning (dangling pointer to ‘candidates’ may be used [-Werror=dangling-pointer=])
Date: Thu, 10 Feb 2022 19:35:28 +0000	[thread overview]
Message-ID: <bug-104492-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104492
           Summary: Bogus dangling pointer warning (dangling pointer to
                    ‘candidates’ may be used [-Werror=dangling-pointer=])
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: thiago at kde dot org
  Target Milestone: ---

Created attachment 52409
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52409&action=edit
Preprocessed sources for qlibrary.cpp

Workaround: https://codereview.qt-project.org/c/qt/qtbase/+/394894
Original sources: 
https://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/plugin/qlibrary.cpp?id=5e378aaff61c9708e0657f3ee29517c06cb075fa#n618
https://github.com/qt/qtbase/blob/5e378aaff61c9708e0657f3ee29517c06cb075fa/src/corelib/plugin/qlibrary.cpp#L618-L677

Code snippet:

    auto isValidSuffix = [](QStringView s) {
        const QLatin1String candidates[] = {
            QLatin1String("so"),
        };
        return std::find(std::begin(candidates), std::end(candidates), s) !=
std::end(candidates);
    };
    auto suffixes = qTokenize(completeSuffix, u'.');
    auto it = suffixes.begin();
    const auto end = suffixes.end();
    while (it != end) {
        if (isValidSuffix(*it++))
          return true;
    }
    return false;

This code above produces the warning:
qlibrary.cpp:114:9: error: dangling pointer to ‘candidates’ may be used
[-Werror=dangling-pointer=]          
  114 |         if (isValidSuffix(*it++))                                       
      |         ^~                                                              
qlibrary.cpp:76:29: note: ‘candidates’ declared here                            
   76 |         const QLatin1String candidates[] = {                            
      |                             ^~~~~~~~~~                                  

The 'candidates' variable has indeed gone out of scope, but there's no use of
its pointer where the lambda is used. The lambda does a std::find, which
returns a pointer into the array, but that pointer is compared to std::end and
the lambda returns a boolean.

Compile the attached preprocessed sources with:
 g++ -march=x86-64-v3 -Wall -Wextra -O3 -o /dev/null -c qlibrary.cpp.ii

GCC commit 1ce5395977f37e8d0c03394f7b932a584ce85cc7 (master branch dated
2022-02-09).

             reply	other threads:[~2022-02-10 19:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 19:35 thiago at kde dot org [this message]
2022-02-10 20:08 ` [Bug c++/104492] " pinskia at gcc dot gnu.org
2022-02-11  0:49 ` [Bug middle-end/104492] [12 Regression] Bogus dangling pointer warning at -O3 msebor at gcc dot gnu.org
2022-02-11  0:59 ` msebor at gcc dot gnu.org
2022-02-11  9:06 ` rguenth at gcc dot gnu.org
2022-02-15  0:40 ` msebor at gcc dot gnu.org
2022-03-09 13:07 ` rguenth at gcc dot gnu.org
2022-03-09 13:07 ` rguenth at gcc dot gnu.org
2022-03-16 16:01 ` msebor at gcc dot gnu.org
2022-04-20  8:52 ` jakub at gcc dot gnu.org
2022-04-25  8:43 ` rguenth at gcc dot gnu.org
2022-04-27 10:03 ` cvs-commit at gcc dot gnu.org
2022-04-27 10:03 ` rguenth at gcc dot gnu.org
2022-04-27 16:48 ` cvs-commit 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-104492-4@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).