public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: gisli.ottarsson@mscsoftware.com
To: gcc-gnats@gcc.gnu.org
Subject: c/8804: gcc fails to warn when function omits a return statement
Date: Tue, 03 Dec 2002 14:16:00 -0000	[thread overview]
Message-ID: <20021203221218.17590.qmail@sources.redhat.com> (raw)


>Number:         8804
>Category:       c
>Synopsis:       gcc fails to warn when function omits a return statement
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Dec 03 14:16:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Gisli Ottarsson
>Release:        gcc (GCC) 3.2 20020822 (Red Hat Linux Rawhide 3.2-4)
>Organization:
>Environment:

>Description:

The following program, which contains an int 
function which fails to return a value, compiles 
without a warning, even with the -pedantic flag.

The program illustrates a form of programmer brain-
damage where the programmer has neglected to type
the 'return' keyword.  This bug can be extremely 
difficult to find but many thankfully, many other 
compilers will catch this and issue a warning/error.
For instance, SGI's compiler warns that: "Non-void 
function "foo" (declared at line 1) should return a 
value."

int foo()
{
  3;
}

int main()
{
  return foo();
}

Please modify gcc so that it issues a warning when it
encounters such mistakes.



>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-12-03 22:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03 14:16 gisli.ottarsson [this message]
2002-12-03 14:23 paolo

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=20021203221218.17590.qmail@sources.redhat.com \
    --to=gisli.ottarsson@mscsoftware.com \
    --cc=gcc-gnats@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).