public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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 11:36:50 +0000 [thread overview]
Message-ID: <bug-99523-4-avAhd8kF6m@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 #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:b08c978f2e18507cbd9853305185665edf05c598
commit r11-7619-gb08c978f2e18507cbd9853305185665edf05c598
Author: Richard Biener <rguenther@suse.de>
Date: Thu Mar 11 10:09:43 2021 +0100
tree-optimization/99523 - missing SSA decls in dumps
This makes sure to dump SSA names without identifier in the
declaration part of a function dump. While we dump the
anonymous variable decls the SSA names referencing them appear
without a clear reference as to what anonymous variable is used
(_3 vs. D.1234).
2021-03-11 Richard Biener <rguenther@suse.de>
PR tree-optimization/99523
* tree-cfg.c (dump_function_to_file): Dump SSA names
w/o identifier to the decls section as well, not only those
without a VAR_DECL.
next prev parent reply other threads:[~2021-03-11 11:36 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 ` [Bug tree-optimization/99523] " rguenth at gcc dot gnu.org
2021-03-11 9:13 ` rguenth at gcc dot gnu.org
2021-03-11 11:36 ` cvs-commit at gcc dot gnu.org [this message]
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-avAhd8kF6m@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: 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).