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 debug/97599] [8/9/10/11 Regression] missing unspecified_parameters DIE in DWARF for functions with variable arguments Date: Wed, 28 Oct 2020 10:00:34 +0000 [thread overview] Message-ID: <bug-97599-4-t7I9NlcAhc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97599-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97599 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aoliva at gcc dot gnu.org --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Adding Alex for debug-stmt / inline-entry etc. issues. Note that clones are materialized only during LTRANS where for example we have no way of generating "nice" DWARF for a clone of a C++ class method. What we _can_ do is create DWARF for an aritificial wrapper function whose body contains an inline copy of said C++ class method (plus required argument marshalling). User (dwarf consumer) expectation is another issue, breakpoints on a function should work and also break on clones. User expectation for OMP outlines is less clear to me. For split functions we shouldn't get two breakpoints (inlined header plus tail) but only break on the header. Ideally the frame of the tail wouldn't even be visible... Note that we do not necessarily outline full scopes in the splitting case, so even abstract origins to scopes might not be a good match there. Maybe don't try to represent the call to the tail as call but handle it as a jump like hot/cold parts of a function (though technically there is a frame).
next prev parent reply other threads:[~2020-10-28 10:00 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-27 17:09 [Bug debug/97599] New: " jakub at gcc dot gnu.org 2020-10-27 17:09 ` [Bug debug/97599] " jakub at gcc dot gnu.org 2020-10-28 7:41 ` rguenth at gcc dot gnu.org 2020-10-28 7:43 ` rguenth at gcc dot gnu.org 2020-10-28 9:10 ` rguenth at gcc dot gnu.org 2020-10-28 9:16 ` jakub at gcc dot gnu.org 2020-10-28 9:58 ` jakub at gcc dot gnu.org 2020-10-28 10:00 ` rguenth at gcc dot gnu.org [this message] 2020-11-14 8:15 ` cvs-commit at gcc dot gnu.org 2020-11-25 11:56 ` cvs-commit at gcc dot gnu.org 2020-11-25 17:18 ` [Bug debug/97599] [8/9 " jakub at gcc dot gnu.org 2021-04-20 23:30 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:48 ` cvs-commit at gcc dot gnu.org 2021-04-22 17:07 ` jakub 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-97599-4-t7I9NlcAhc@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).