public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/99523] New: Declarations for variable names missing in GIMPLE dump
Date: Wed, 10 Mar 2021 17:10:51 +0000 [thread overview]
Message-ID: <bug-99523-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99523
Bug ID: 99523
Summary: Declarations for variable names missing in GIMPLE dump
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: acoplan at gcc dot gnu.org
Target Milestone: ---
For the following testcase:
int f(__builtin_va_list *ap) { return __builtin_va_arg(*ap, int); }
on AArch64 at -O2 with -fdump-tree-optimized=-, we get:
;; Function f (f, funcdef_no=0, decl_uid=3583, cgraph_uid=1, symbol_order=0)
f (struct * ap)
{
int D.3591;
void * D.3592;
int * iftmp.2;
sizetype D.3596;
sizetype D.3597;
sizetype D.3598;
void * D.3599;
int D.3601;
int * iftmp.3;
void * D.3607;
sizetype D.3608;
int _4;
<bb 2> [local count: 1073741824]:
_9 = ap_2(D)->__gr_offs;
_10 = ap_2(D)->__stack;
if (_9 >= 0)
goto <bb 3>; [59.00%]
else
goto <bb 4>; [41.00%]
where the variables _9 and _10 are apparently missing declarations in the IR
dump. I believe the variables came from calls to get_initialized_tmp_var in
aarch64_gimplify_va_arg_expr.
Not sure if this is some missing bookkeeping around the gimplification or
perhaps a bug in the dumping code?
next reply other threads:[~2021-03-10 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 17:10 acoplan at gcc dot gnu.org [this message]
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
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@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).