public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gprocida at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111788] g++ DWARF for void foo(...) missing unspecified parameters DIE
Date: Wed, 08 Nov 2023 11:13:56 +0000	[thread overview]
Message-ID: <bug-111788-4-AK67xszpil@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111788-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111788

--- Comment #4 from Giuliano Procida <gprocida at google dot com> ---
Also worth noting that while Clang gives virtual table entries (for struct X)
this type in DWARF:

int(** _vptr.X)(...)

GCC gives them this type:

int(** _vptr$X)()

The different member names are an unfortunate inconsistency.

Clang is strictly better on the typing, stating that the virtual functions take
an unknown number of arguments. Perhaps even better would have been if the
first argument had been specified as type X*.

In any case, this is likely all cosmetic as debuggers have all the special
knowledge needed.

      parent reply	other threads:[~2023-11-08 11:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 16:00 [Bug c++/111788] New: " gprocida at google dot com
2023-10-12 16:05 ` [Bug c++/111788] " pinskia at gcc dot gnu.org
2023-10-13  6:50 ` rguenth at gcc dot gnu.org
2023-10-13  7:02 ` gprocida at google dot com
2023-11-08 11:13 ` gprocida at google dot com [this message]

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-111788-4-AK67xszpil@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).