public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7311: inline functions do not give control reaches end of non-void function in g++
Date: Mon, 15 Jul 2002 06:26:00 -0000	[thread overview]
Message-ID: <20020715132601.12589.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/7311; it has been noted by GNATS.

From: Andrew Pinski <pinskia@physics.uc.edu>
To: Bas Wijnen <shevek@fmf.nl>
Cc: gcc-gnats@gcc.gnu.org, <debian-gcc@lists.debian.org>
Subject: Re: c++/7311: inline functions do not give control reaches end of non-void function in g++
Date: Mon, 15 Jul 2002 09:19:50 -0400

 This has been fixed in gcc version 3.3 20020713 (experimental) at least.
 
 Thanks,
 Andrew Pinski
 
 On Monday, July 15, 2002, at 08:30 , Bas Wijnen wrote:
 
 > class foo
 > {
 > public:
 >   int bar ()
 >   {
 >   }
 > };
 >
 > int main ()
 > {
 >   foo f;
 >   f.bar ();
 >   return 0;
 > }
 


             reply	other threads:[~2002-07-15 13:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-15  6:26 Andrew Pinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-15  5:36 Bas Wijnen

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=20020715132601.12589.qmail@sources.redhat.com \
    --to=pinskia@physics.uc.edu \
    --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).