public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/55541] [4.6/4.7/4.8 Regression] unable to see local variables due extra lexical block was generated Date: Fri, 30 Nov 2012 10:35:00 -0000 [thread overview] Message-ID: <bug-55541-4-WEO7PXgbZ8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55541-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55541 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-11-30 10:35:06 UTC --- That is the result of 13701 /* Make it so that `main' always returns 0 by default. */ 13702 if (DECL_MAIN_P (current_function_decl)) 13703 finish_return_stmt (integer_zero_node); in C++ finish_function (and for C99 similarly): if (MAIN_NAME_P (DECL_NAME (fndecl)) && flag_hosted && TYPE_MAIN_VARIANT (TREE_TYPE (TREE_TYPE (fndecl))) == integer_type_node && flag_isoc99) { /* Hack. We don't want the middle-end to warn that this return is unreachable, so we mark its location as special. Using UNKNOWN_LOCATION has the problem that it gets clobbered in annotate_one_with_locus. A cleaner solution might be to ensure ! should_carry_locus_p (stmt), but that needs a flag. */ c_finish_return (BUILTINS_LOCATION, integer_zero_node, NULL_TREE); } Both these add the stmts after the function body, which is usually just a BIND_EXPR containing all the stuff from the source in its operand in a statement list. We'd need to arrange for this, if the whole function body so far is a single BIND_EXPR, to stick it at the end of the sequence in the BIND_EXPR.
next prev parent reply other threads:[~2012-11-30 10:35 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-30 2:55 [Bug c++/55541] New: " chihin.ko at oracle dot com 2012-11-30 9:05 ` [Bug debug/55541] " paolo.carlini at oracle dot com 2012-11-30 9:22 ` [Bug debug/55541] [4.6/4.7/4.8 Regression] " rguenth at gcc dot gnu.org 2012-11-30 10:35 ` jakub at gcc dot gnu.org [this message] 2012-11-30 13:04 ` jakub at gcc dot gnu.org 2012-11-30 19:15 ` jason at gcc dot gnu.org 2012-12-05 16:24 ` jason at gcc dot gnu.org 2012-12-06 15:07 ` jakub at gcc dot gnu.org 2012-12-06 16:18 ` rguenth at gcc dot gnu.org 2013-04-12 15:15 ` [Bug debug/55541] [4.7/4.8/4.9 " jakub at gcc dot gnu.org 2014-06-12 13:42 ` [Bug debug/55541] [4.7/4.8/4.9/4.10 " rguenth at gcc dot gnu.org 2014-12-19 13:35 ` [Bug debug/55541] [4.8/4.9/5 " jakub at gcc dot gnu.org 2015-02-05 14:52 ` jakub at gcc dot gnu.org 2015-02-05 16:26 ` jakub at gcc dot gnu.org 2015-02-05 17:56 ` jakub at gcc dot gnu.org 2015-02-12 18:27 ` [Bug debug/55541] [4.8/4.9 " jakub at gcc dot gnu.org 2015-06-23 8:16 ` rguenth at gcc dot gnu.org 2015-06-26 20:04 ` [Bug debug/55541] [4.9 " jakub at gcc dot gnu.org 2015-06-26 20:34 ` jakub 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-55541-4-WEO7PXgbZ8@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).