public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "simon.marchi at polymtl dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/96937] Duplicate DW_TAG_formal_parameter in out-of-line DW_TAG_subprogram instance
Date: Tue, 08 Sep 2020 13:22:26 +0000 [thread overview]
Message-ID: <bug-96937-4-4l6ftL0naO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96937-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96937
--- Comment #5 from Simon Marchi <simon.marchi at polymtl dot ca> ---
(In reply to Richard Biener from comment #3)
> Hmm, can you point out the issue in the reduced testcase? I can't see it.
> The only cloning done I see is partial inlining so does
> -fno-partial-inlining fix the issue for you?
Doh, I indeed uploaded the wrong thing. My creduce test was trying to
reproduce the "wrong parameter order" problem, which I later found was probably
not considered a bug, instead of the "duplicate parameter problem". I re-ran
it with the right test, I attached the result.
The relevant portion of the DWARF is:
0x000003bb: DW_TAG_subprogram
DW_AT_abstract_origin (0x00000383 "do_examine")
DW_AT_low_pc (0x0000000000000000)
DW_AT_high_pc (0x0000000000000039)
DW_AT_frame_base (DW_OP_call_frame_cfa)
DW_AT_GNU_all_call_sites (true)
DW_AT_sibling (0x00000464)
0x000003d6: DW_TAG_variable
DW_AT_abstract_origin (0x000003a4 "ai")
0x000003db: DW_TAG_variable
DW_AT_abstract_origin (0x000003af "aq")
DW_AT_location (DW_OP_fbreg -17)
0x000003e3: DW_TAG_formal_parameter
DW_AT_abstract_origin (0x0000039f)
DW_AT_location (<decoding error> 9f 03 00 00 9f)
0x000003ef: DW_TAG_formal_parameter
DW_AT_abstract_origin (0x0000039a)
DW_AT_location (<decoding error> 9a 03 00 00 9f)
0x000003fb: DW_TAG_formal_parameter
DW_AT_abstract_origin (0x00000390 "y")
0x00000400: DW_TAG_formal_parameter
DW_AT_abstract_origin (0x00000390 "y")
The last two DW_TAG_formal_parameter refer to the same parameter.
next prev parent reply other threads:[~2020-09-08 13:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 14:06 [Bug debug/96937] New: " simon.marchi at polymtl dot ca
2020-09-04 14:07 ` [Bug debug/96937] " simon.marchi at polymtl dot ca
2020-09-04 14:09 ` simon.marchi at polymtl dot ca
2020-09-07 5:49 ` rguenth at gcc dot gnu.org
2020-09-08 13:20 ` simon.marchi at polymtl dot ca
2020-09-08 13:22 ` simon.marchi at polymtl dot ca [this message]
2021-12-09 16:35 ` wcohen at redhat dot com
2021-12-09 16:40 ` wcohen at redhat dot com
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-96937-4-4l6ftL0naO@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).