public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/28901] unable to resolve function overloads involving inheritance
Date: Thu, 24 Feb 2022 21:26:32 +0000	[thread overview]
Message-ID: <bug-28901-4717-2NWpxWQQoq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28901-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28901

--- Comment #11 from Martin Sebor <msebor at gmail dot com> ---
I'm not having any luck isolating the problem from LLVM to a standalone test
case.  I can't even recreate it within LLVM if I replace llvm::raw_ostream with
an exact copy of it (llvm::xxx_raw_ostream).  There's something about
llvm::raw_ostream that GDB doesn't like.

With a copy of raw_ostream called xraw_ostream and the code below in
SimplifyLibCalls.cpp:

struct Foo
{
  void foo(xxx_raw_ostream &);
  void foo(xxx_raw_ostream &, int);

  void bar(raw_ostream &);
  void bar(raw_ostream &, int);
};

void Foo::foo(xxx_raw_ostream &) { }
void Foo::foo(xxx_raw_ostream &, int) { }

void Foo::bar(raw_ostream &) { }
void Foo::bar(raw_ostream &, int) { }

GDB can resolve the call pfoo->foo (xr) but not pfoo->bar (r) (with pfoo being
a pointer to Foo, xr a reference to xxx_raw_ostream, and r a reference to
raw_ostream).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-02-24 21:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 23:56 [Bug c++/28901] New: " msebor at gmail dot com
2022-02-18 17:14 ` [Bug c++/28901] " tromey at sourceware dot org
2022-02-18 21:07 ` tromey at sourceware dot org
2022-02-18 22:07 ` msebor at gmail dot com
2022-02-18 22:11 ` tromey at sourceware dot org
2022-02-18 22:19 ` msebor at gmail dot com
2022-02-19  2:24 ` tromey at sourceware dot org
2022-02-19 16:29 ` tromey at sourceware dot org
2022-02-23 20:17 ` tromey at sourceware dot org
2022-02-23 20:23 ` msebor at gmail dot com
2022-02-23 20:23 ` cvs-commit at gcc dot gnu.org
2022-02-24 21:26 ` msebor at gmail dot com [this message]
2022-03-12 22:12 ` tromey at sourceware dot org
2022-11-09 15:36 ` tromey at sourceware dot org
2022-11-10 12:19 ` blarsen 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-28901-4717-2NWpxWQQoq@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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).