public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/4210] should not warn in dead code Date: Wed, 06 May 2020 16:27:14 +0000 [thread overview] Message-ID: <bug-4210-4-MGMNM9VNGN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-4210-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=4210 Eric Gallager <egallager at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |egallager at gcc dot gnu.org --- Comment #40 from Eric Gallager <egallager at gcc dot gnu.org> --- (In reply to Manuel López-Ibáñez from comment #39) > I think these questions are more appropriate for the mailing list, since > few people are subscribed to this bug. There were more previously, but a lot of people got dropped from cc lists all throughout bugzilla in the process of transferring servers... I was on this one previously, for example, but now I'm having to re-subscribe... > > You can easily find which pass does something by dumping (-ftree-dump-*) > all of them and comparing them. > > On Wed, 6 May 2020, 09:11 nisse at lysator dot liu.se, < > gcc-bugzilla@gcc.gnu.org> wrote: > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=4210 > > > > --- Comment #38 from Niels Möller <nisse at lysator dot liu.se> --- > > Just a brief update. > > > > 1. Tried adding fprintf warnings to c_gimplify_expr (btw, what's the right > > way > > to display a pretty warning with line numbers etc in later passes?). But it > > seems that's too early, I still get warnings for dead code. > > > > 2. The pass_remove_useless_stmts, mentioned in the docs, was deleted in > > 2009 > > (see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41573), and I take it > > it was > > obsoleted earlier, since there's no mention of a replacement. So what pass > > should I look at that is related to basic control flow analysis, and > > discarding > > unreachable statements? > > > > -- > > You are receiving this mail because: > > You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-06 16:27 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-4210-4@http.gcc.gnu.org/bugzilla/> 2014-03-13 2:10 ` [Bug middle-end/4210] should not warning with " pinskia at gcc dot gnu.org 2014-08-09 6:09 ` pinskia at gcc dot gnu.org 2020-04-26 21:28 ` nisse at lysator dot liu.se 2020-05-04 20:44 ` nisse at lysator dot liu.se 2020-05-05 2:17 ` vincent-gcc at vinc17 dot net 2020-05-05 15:43 ` [Bug middle-end/4210] should not warn in " msebor at gcc dot gnu.org 2020-05-05 17:54 ` manu at gcc dot gnu.org 2020-05-05 18:26 ` nisse at lysator dot liu.se 2020-05-05 18:39 ` nisse at lysator dot liu.se 2020-05-06 8:10 ` nisse at lysator dot liu.se 2020-05-06 15:37 ` lopezibanez at gmail dot com 2020-05-06 16:27 ` egallager at gcc dot gnu.org [this message] 2020-05-06 18:44 ` nisse at lysator dot liu.se 2020-06-04 21:02 ` nisse at lysator dot liu.se 2020-06-05 11:14 ` glisse at gcc dot gnu.org
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=bug-4210-4-MGMNM9VNGN@http.gcc.gnu.org/bugzilla/ \ --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).