public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xvladsoft at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109554] Compiler generates incorrect code when the function declared with returned parameterm but no 'return' in its body
Date: Wed, 19 Apr 2023 14:29:39 +0000 [thread overview]
Message-ID: <bug-109554-4-G5uJ1vF116@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109554-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109554
Khokholkov Vladimir <xvladsoft at yahoo dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|INVALID |WONTFIX
--- Comment #3 from Khokholkov Vladimir <xvladsoft at yahoo dot com> ---
(In reply to Xi Ruoyao from comment #2)
> And it's clearly documented in https://gcc.gnu.org/gcc-8/changes.html:
>
> Flowing off the end of a non-void function is considered unreachable and may
> be subject to optimization on that basis. As a result of this change,
> -Wreturn-type warnings are enabled by default for C++.
>
> If you insist on ignoring the -Wreturn-type warning, you are doing things
> wrong.
I see...
Ok, thanks!
I think the issue should be closed then.
(P.S. I do not ignore that message, just accidentally found this case and
decided to investigate).
B.R.
Vladimir.
next prev parent reply other threads:[~2023-04-19 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 11:47 [Bug c/109554] New: " xvladsoft at yahoo dot com
2023-04-19 11:54 ` [Bug c/109554] " schwab@linux-m68k.org
2023-04-19 11:56 ` [Bug c++/109554] " xry111 at gcc dot gnu.org
2023-04-19 14:29 ` xvladsoft at yahoo dot com [this message]
2023-04-19 15:15 ` schwab@linux-m68k.org
2023-06-27 17:51 ` 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-109554-4-G5uJ1vF116@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).