public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104787] New: [12 Regression] False positive -Wreturn-type since r12-5638-ga3e75c1491cd2d50
Date: Fri, 04 Mar 2022 15:46:46 +0000	[thread overview]
Message-ID: <bug-104787-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104787
           Summary: [12 Regression] False positive -Wreturn-type since
                    r12-5638-ga3e75c1491cd2d50
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: jason at gcc dot gnu.org
  Target Milestone: ---

Similarly to PR103597, the following triggers false positive without an
optimization level (reduced from godot game engine):

$ cat godot.ii
struct String {
  String(const char *);
};
struct FileAccessRef {
  FileAccessRef(int);
  ~FileAccessRef();
};
struct OS_LinuxBSD {
  String get_processor_name() const;
};
String OS_LinuxBSD::get_processor_name() const {
  FileAccessRef f = 0;
  if (true)
    return "";
}

$ g++ godot.ii -Werror=return-type -c
godot.ii: In member function ‘String OS_LinuxBSD::get_processor_name() const’:
godot.ii:15:1: error: control reaches end of non-void function
[-Werror=return-type]
   15 | }
      | ^
cc1plus: some warnings being treated as errors

             reply	other threads:[~2022-03-04 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 15:46 marxin at gcc dot gnu.org [this message]
2022-03-04 15:46 ` [Bug c++/104787] " marxin at gcc dot gnu.org
2022-03-05  0:38 ` pinskia at gcc dot gnu.org
2022-03-28 16:06 ` [Bug middle-end/104787] " jason at gcc dot gnu.org
2022-05-06  8:32 ` [Bug middle-end/104787] [12/13 " jakub at gcc dot gnu.org
2022-06-01 19:41 ` jason at gcc dot gnu.org
2022-07-26 12:56 ` rguenth at gcc dot gnu.org
2023-01-27 19:39 ` pinskia at gcc dot gnu.org
2023-05-08 12:24 ` [Bug middle-end/104787] [12/13/14 " rguenth 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-104787-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).