[Bug c++/11474] -Wreturn-type should default to on when compiling C++

[Bug c++/11474] -Wreturn-type should default to on when compiling C++

[redi at gcc dot gnu.org]

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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=55189

--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
PR 55189 made it on by default for GCC 8.

[Bug c++/11474] -Wreturn-type should default to on when compiling C++

[bangerth at dealii dot org]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11474



------- Additional Comments From bangerth at dealii dot org  2003-07-14 15:12 -------
You're certainly right with your argument :-) I guess I should have stated my
underlying assumption: don't have _any_ warnings on by default. I understand
that's not the present state, though.

W.

[Bug c++/11474] -Wreturn-type should default to on when compiling C++

[gdr at integrable-solutions dot net]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11474



------- Additional Comments From gdr at integrable-solutions dot net  2003-07-14 14:54 -------
Subject: Re:  -Wreturn-type should default to on when compiling C++

"bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> writes:

| What's wrong with asking people to please compile their code with -W -Wall?

In some circumstances, there are not practical.  
I do not have strong feelings about warning by default.  

| There are good reasons for most of the warning flags we have,

there are reasons we have flags.  That they are "good" depends on your
definition of "good", and is certainly a matter of debate.  The issue
is whether the warning should be on by default or not.  
The same arguments you're making can be used for having the warning on
by default and telling people  to use the -Wno- corresponding flags.
As you can see, the line you're reasoning cannot be  determining.

| so people should
| just learn to use warning flags. It's not gcc's task to _think_  for
| programmers unless they specifically ask for it.

But it just does that by deciding which flags to turn off by default! 

-- Gaby

[Bug c++/11474] -Wreturn-type should default to on when compiling C++

[bangerth at dealii dot org]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11474



------- Additional Comments From bangerth at dealii dot org  2003-07-14 14:40 -------
What's wrong with asking people to please compile their code with -W -Wall?
There are good reasons for most of the warning flags we have, so people should
just learn to use warning flags. It's not gcc's task to _think_  for
programmers unless they specifically ask for it.

By the same argument, we also don't switch on optimizations by default, but ask
people to do so explicitly on the command line.

W.

[Bug c++/11474] -Wreturn-type should default to on when compiling C++

[jsm at polyomino dot org dot uk]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11474



------- Additional Comments From jsm at polyomino dot org dot uk  2003-07-13 16:51 -------
Subject: Re:  -Wreturn-type should default to on when compiling
 C++

On Sun, 13 Jul 2003, zack at gcc dot gnu dot org wrote:

> I don't think we can reject the program by default in either C or C++,
> but I would support turning the warning on by default in both languages --
> the condition it warns about is guaranteed to be a bug (unless the code
> predates the existence of the 'void' return type, and even then the fix is
> trivial)

The most obvious problematic cases are where control can't reach the end
of the function because of a call to a nonreturning function, but the
maintainer wants to avoid annotations specific to a particular compiler
(in this case, __attribute__((__noreturn__))) in their source code so the
compiler doesn't know that the function is nonreturning.

[Bug c++/11474] -Wreturn-type should default to on when compiling C++

[lloyd at randombit dot net]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11474



------- Additional Comments From lloyd at randombit dot net  2003-07-13 16:39 -------
Obviously I was wrong about it being an standard-mandated diagnostic (I suppose
I should have checked the standard first, I just assumed). However, if the
behavior when encoutering this is undefined, then a warning is fine as far as
the standard is concerned, correct?

[Bug c++/11474] -Wreturn-type should default to on when compiling C++

[zack at gcc dot gnu dot org]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11474



------- Additional Comments From zack at gcc dot gnu dot org  2003-07-13 08:22 -------
I don't think we can reject the program by default in either C or C++,
but I would support turning the warning on by default in both languages --
the condition it warns about is guaranteed to be a bug (unless the code
predates the existence of the 'void' return type, and even then the fix is
trivial)

[Bug c++/11474] -Wreturn-type should default to on when compiling C++

[gdr at integrable-solutions dot net]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11474



------- Additional Comments From gdr at integrable-solutions dot net  2003-07-13 07:41 -------
Subject: Re:  -Wreturn-type should default to on when compiling C++

"bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> writes:

| No. 6.6.3/2 says
|   [...] Flowing off the end of a function is equivalent to a return with
|   no value; this results in undefined behavior in a value-returning
|   function.
| 
| It specifically does not say that a diagnostic is required.

a diagnostic is required only  for diagnosable rules, and
"undefined behaviour" is not one.

-- Gaby

[Bug c++/11474] -Wreturn-type should default to on when compiling C++

[gdr at integrable-solutions dot net]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11474



------- Additional Comments From gdr at integrable-solutions dot net  2003-07-13 07:40 -------
Subject: Re:  New: -Wreturn-type should default to on when compiling C++

"lloyd at randombit dot net" <gcc-bugzilla@gcc.gnu.org> writes:

| This is pretty simple - when using C++, -Wreturn-type should a) always be on,
| and b) always cause an error, since not returning correctly from the function
| is ALWAYS an error in C++

The last statement is untrue.  

-- Gaby

[Bug c++/11474] -Wreturn-type should default to on when compiling C++

[bangerth at dealii dot org]

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11474


bangerth at dealii dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


------- Additional Comments From bangerth at dealii dot org  2003-07-09 14:39 -------
No. 6.6.3/2 says
  [...] Flowing off the end of a function is equivalent to a return with
  no value; this results in undefined behavior in a value-returning
  function.

It specifically does not say that a diagnostic is required.

W.