public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@adacore.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [Patch] Fix bogus 'function does return' warning
Date: Fri, 16 Oct 2009 09:55:00 -0000	[thread overview]
Message-ID: <200910161155.29857.ebotcazou@adacore.com> (raw)
In-Reply-To: <84fc9c000910160244l6e38fdc9ga9063d8a047e58bb@mail.gmail.com>

> Huh.  I wonder why the unreachable blocks are not removed
> after CFG build?  After all noreturn calls end BBs.

It's -O0 so the compiler doesn't see that <L17> is unreachable:

<L17>:
  return;

<L19>:
  finally_tmp.10 = 1;
  p.error (); [static-chain: &FRAME.8]
  switch (finally_tmp.10) <default: <L17>, case 1: <L20>>

-- 
Eric Botcazou

  reply	other threads:[~2009-10-16  9:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15 19:51 Eric Botcazou
2009-10-16  9:50 ` Richard Guenther
2009-10-16  9:55   ` Eric Botcazou [this message]
2009-10-16 10:38     ` Richard Guenther
2009-10-16 11:12       ` Eric Botcazou
2009-10-16 11:32         ` Richard Guenther
2009-10-16 13:21           ` Eric Botcazou
2009-10-17 10:26             ` Eric Botcazou
2009-10-17 11:29               ` Richard Guenther
2009-10-17 11:36                 ` Eric Botcazou
2009-10-17 14:12                   ` Richard Guenther
2009-10-17 17:00                     ` Richard Henderson
2009-10-17 17:10                       ` Richard Guenther
2009-10-18 15:49                         ` Eric Botcazou
2009-10-18 16:36                           ` Richard Henderson
2009-10-18 18:41                             ` Eric Botcazou
2009-10-19 15:39                               ` Richard Henderson
2009-10-19 17:32                                 ` Eric Botcazou
2009-10-19 18:30                                   ` Richard Henderson

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=200910161155.29857.ebotcazou@adacore.com \
    --to=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    /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).