This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gcc (lack of) return type warnings

From: "Manuel López-Ibáñez" <lopezibanez at gmail dot com>
To: "Andreas Schwab" <schwab at suse dot de>
Cc: "Tobias Pflug" <tobias dot pflug at exorbyte dot com>, gcc at gcc dot gnu dot org
Date: Wed, 14 Feb 2007 15:55:05 +0000
Subject: Re: gcc (lack of) return type warnings
References: <45D319AB.5010209@exorbyte.com> <je4pposrs3.fsf@sykes.suse.de> <45D326B7.5060702@exorbyte.com> <jezm7grbu8.fsf@sykes.suse.de>

On 14/02/07, Andreas Schwab <schwab@suse.de> wrote:

Tobias Pflug <tobias.pflug@exorbyte.com> writes:

> That's not desirable is it ?
If you are concerned, you are free to use -Wreturn-type.  There are many
types of undefined behaviour that are not warned by default.


And Wreturn-type is enabled by -Wall. Moreover, there are many types
of undefined behaviour that are not warned at all!

Gabriel is working on a new -Wundefined option (PR 30334), so if you
find any of those, or you think that this should be warned
independently of -Wreturn-type, please add a comment to the PR.
Perhaps -Wundefined could be enabled by default like -Woverflow.

Cheers,

Manuel.

References:
- gcc (lack of) return type warnings
  - From: Tobias Pflug
- Re: gcc (lack of) return type warnings
  - From: Andreas Schwab
- Re: gcc (lack of) return type warnings
  - From: Tobias Pflug
- Re: gcc (lack of) return type warnings
  - From: Andreas Schwab

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]