public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/20624] [4.0 Regression] wrong "control reaches end of non-void function" warning Date: Fri, 19 Aug 2005 05:56:00 -0000 [thread overview] Message-ID: <20050819054146.28526.qmail@sourceware.org> (raw) In-Reply-To: <20050324162738.20624.oliverst@online.de> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-08-19 05:41 ------- Subject: Bug 20624 CVSROOT: /cvs/gcc Module name: gcc Changes by: pinskia@gcc.gnu.org 2005-08-19 05:41:14 Modified files: gcc : ChangeLog gimple-low.c gcc/testsuite : ChangeLog Added files: gcc/testsuite/g++.dg/warn: Wreturn-3.C Log message: 2005-08-19 Andrew Pinski <pinskia@physics.uc.edu> PR middle-end/20624 * g++.dg/warn/Wreturn-3.C: New test 2005-08-19 Andrew Pinski <pinskia@physics.uc.edu> PR middle-end/20624 * gimple-low.c (block_may_fallthru): Handle CLEANUP_POINT_EXPR by looking past it. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.9776&r2=2.9777 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/gimple-low.c.diff?cvsroot=gcc&r1=2.26&r2=2.27 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&r1=1.5936&r2=1.5937 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/warn/Wreturn-3.C.diff?cvsroot=gcc&r1=NONE&r2=1.1 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20624
next prev parent reply other threads:[~2005-08-19 5:41 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-03-24 16:27 [Bug c++/20624] New: " oliverst at online dot de 2005-03-24 16:30 ` [Bug c++/20624] " pinskia at gcc dot gnu dot org 2005-03-24 16:31 ` [Bug middle-end/20624] " pinskia at gcc dot gnu dot org 2005-03-24 16:54 ` oliverst at online dot de 2005-03-24 17:10 ` pinskia at gcc dot gnu dot org 2005-03-24 17:18 ` pinskia at gcc dot gnu dot org 2005-03-24 17:32 ` oliverst at online dot de 2005-03-24 18:03 ` [Bug middle-end/20624] [4.0/4.1 Regression] " pinskia at gcc dot gnu dot org 2005-03-25 2:03 ` [Bug c++/20624] " oliverst at online dot de 2005-03-29 9:59 ` oliverst at online dot de 2005-04-08 21:46 ` mmitchel at gcc dot gnu dot org 2005-04-09 17:01 ` pinskia at gcc dot gnu dot org 2005-04-21 5:06 ` mmitchel at gcc dot gnu dot org 2005-07-08 1:41 ` mmitchel at gcc dot gnu dot org 2005-08-17 15:55 ` pinskia at gcc dot gnu dot org 2005-08-17 15:59 ` pinskia at gcc dot gnu dot org 2005-08-17 19:31 ` pinskia at gcc dot gnu dot org 2005-08-17 21:54 ` steven at gcc dot gnu dot org 2005-08-17 22:35 ` pinskia at gcc dot gnu dot org 2005-08-17 23:02 ` pinskia at gcc dot gnu dot org 2005-08-18 20:43 ` pinskia at gcc dot gnu dot org 2005-08-19 5:41 ` [Bug c++/20624] [4.0 " pinskia at gcc dot gnu dot org 2005-08-19 5:56 ` cvs-commit at gcc dot gnu dot org [this message] 2005-08-20 20:37 ` cvs-commit at gcc dot gnu dot org 2005-08-20 20:38 ` pinskia at gcc dot gnu dot org [not found] <bug-20624-9121@http.gcc.gnu.org/bugzilla/> 2008-04-16 8:04 ` pluto at agmk dot net 2008-04-21 13:08 ` manu at gcc dot gnu dot org 2008-04-21 13:15 ` pluto at agmk dot net 2008-04-23 9:25 ` pluto at agmk dot net 2008-05-17 0:02 ` pinskia at gcc dot gnu dot org [not found] <bug-20624-4@http.gcc.gnu.org/bugzilla/> 2012-05-24 13:59 ` peter777778 at hotmail dot co.uk
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=20050819054146.28526.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).