public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/99523] Declarations for variable names missing in GIMPLE dump Date: Thu, 11 Mar 2021 08:27:30 +0000 [thread overview] Message-ID: <bug-99523-4-rZVqegIk9c@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99523-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99523 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- They are there, it's the sizetype D.3596; sizetype D.3597; sizetype D.3598; void * D.3599; int D.3601; etc. variables, but they are DECL_IGNORED (they have no "name") and so dumping which does case SSA_NAME: if (SSA_NAME_IDENTIFIER (node)) { if ((flags & TDF_NOUID) && SSA_NAME_VAR (node) && DECL_NAMELESS (SSA_NAME_VAR (node))) dump_fancy_name (pp, SSA_NAME_IDENTIFIER (node)); else if (! (flags & TDF_GIMPLE) || SSA_NAME_VAR (node)) dump_generic_node (pp, SSA_NAME_IDENTIFIER (node), spc, flags, false); } pp_underscore (pp); pp_decimal_int (pp, SSA_NAME_VERSION (node)); if (SSA_NAME_IS_DEFAULT_DEF (node)) pp_string (pp, "(D)"); if (SSA_NAME_OCCURS_IN_ABNORMAL_PHI (node)) pp_string (pp, "(ab)"); break; sees a NULL SSA_NAME_IDENTIFIER. I suppose diff --git a/gcc/tree-cfg.c b/gcc/tree-cfg.c index d04ce212561..4e40b7c0155 100644 --- a/gcc/tree-cfg.c +++ b/gcc/tree-cfg.c @@ -8155,7 +8155,7 @@ dump_function_to_file (tree fndecl, FILE *file, dump_flags_t flags) if (gimple_in_ssa_p (cfun)) FOR_EACH_SSA_NAME (ix, name, cfun) { - if (!SSA_NAME_VAR (name)) + if (!SSA_NAME_IDENTIFIER (name)) { fprintf (file, " "); print_generic_expr (file, TREE_TYPE (name), flags); would display them similar to anonymous SSA names (but then the dumped decls above are redundant and useless). The testcase shows the same on x86_64 btw.
next prev parent reply other threads:[~2021-03-11 8:27 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-10 17:10 [Bug tree-optimization/99523] New: " acoplan at gcc dot gnu.org 2021-03-11 8:27 ` rguenth at gcc dot gnu.org [this message] 2021-03-11 9:13 ` [Bug tree-optimization/99523] " rguenth at gcc dot gnu.org 2021-03-11 11:36 ` cvs-commit at gcc dot gnu.org 2021-03-11 11:38 ` rguenth at gcc dot gnu.org 2021-03-11 12:07 ` acoplan 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-99523-4-rZVqegIk9c@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).