public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: "Thomas König" <tkoenig@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc/devel/coarray_native] Set DECL_ARTIFICIAL on gfortran internal variables. Date: Sun, 20 Dec 2020 15:37:36 +0000 (GMT) [thread overview] Message-ID: <20201220153736.13A2E3857804@sourceware.org> (raw) https://gcc.gnu.org/g:a039ddac6d248f06184f1eece05d1da513917d69 commit a039ddac6d248f06184f1eece05d1da513917d69 Author: Thomas Koenig <tkoenig@gcc.gnu.org> Date: Sun Dec 20 16:27:01 2020 +0100 Set DECL_ARTIFICIAL on gfortran internal variables. It seems we sometimes use DECL_ARTIFICIAL as choosing between different code paths. In order not to make -fdebug-aux-vars do different things, set DECL_ARTIFICIAL on the variables to avoid these different code paths (and the corresponding regressions). gcc/fortran/ChangeLog: * trans.c (create_var_debug_raw): Set DECL_ARTIFICIAL on variables. (cherry picked from commit 8d76c007afe4c70f51fd56b0e5b89522de5de61f) Diff: --- gcc/fortran/trans.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/gcc/fortran/trans.c b/gcc/fortran/trans.c index fa7fd9d88aa..57a344a63c9 100644 --- a/gcc/fortran/trans.c +++ b/gcc/fortran/trans.c @@ -128,6 +128,9 @@ create_var_debug_raw (tree type, const char *prefix) t = build_decl (input_location, VAR_DECL, get_identifier (name_buf), type); + /* Not setting this causes some regressions. */ + DECL_ARTIFICIAL (t) = 1; + /* We want debug info for it. */ DECL_IGNORED_P (t) = 0; /* It should not be nameless. */
reply other threads:[~2020-12-20 15:37 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201220153736.13A2E3857804@sourceware.org \ --to=tkoenig@gcc.gnu.org \ --cc=gcc-cvs@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).