public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: steven@gcc.gnu.org
To: am-99173@konami.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, steven@gcc.gnu.org
Subject: Re: optimization/7189: [3.2/3.3 regression] gcc -O2 -Wall does not print ``control reaches end of non-void function'' warning
Date: Tue, 11 Mar 2003 20:09:00 -0000	[thread overview]
Message-ID: <20030311200911.4595.qmail@sources.redhat.com> (raw)

Old Synopsis: [3.2/3.3/3.4 regression] gcc -O2 -Wall does not print ``control reaches end of non-void function'' warning
New Synopsis: [3.2/3.3 regression] gcc -O2 -Wall does not print ``control reaches end of non-void function'' warning

Responsible-Changed-From-To: unassigned->steven
Responsible-Changed-By: steven
Responsible-Changed-When: Tue Mar 11 20:09:11 2003
Responsible-Changed-Why:
    Already fixed on mainline with my patch.  Waiting for approval for 3.3.  Will have to backport to 3.2 too...

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7189


                 reply	other threads:[~2003-03-11 20:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030311200911.4595.qmail@sources.redhat.com \
    --to=steven@gcc.gnu.org \
    --cc=am-99173@konami.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).