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: Fri, 18 Feb 2022 22:07:50 +0000	[thread overview]
Message-ID: <bug-28901-4717-F4h5ZkMjbq@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 #3 from Martin Sebor <msebor at gmail dot com> ---
Thanks for the quick patch!  I can confirm it fixes the test case I submitted
but it doesn't seem to help with the LLVM use case.  I still get the same error
-- see below.  Let me see if I can reduce it to a test case.

Breakpoint 1, llvm::LibCallSimplifier::optimizeStrLen (this=0x7fffffff6898,
CI=0x986a2a0, B=...) at
/src/llvm/llvm/lib/Transforms/Utils/SimplifyLibCalls.cpp:726
726       if (Value *V = optimizeStringLength(CI, B, 8))
(gdb) p CI
$1 = (llvm::CallInst *) 0x986a2a0
(gdb) p errs()
$2 = (llvm::raw_fd_ostream &) @0x979fe40: {<llvm::raw_pwrite_stream> =
{<llvm::raw_ostream> = {
  ...
(gdb) p (llvm::Value*)CI
$3 = (llvm::Value *) 0x986a2a0
(gdb) p *$3
$4 = {VTy = 0x9862c00, UseList = 0x986a350, SubclassID = 83 'S', 
  ...
(gdb) p $3->print($2, false) 
Cannot resolve method llvm::Value::print to any overloaded instance

(gdb) ptype $3
type = class llvm::Value {
  ...
  public:
    llvm::Value & operator=(const llvm::Value &);
    void deleteValue(void);
    void dump(void) const;
    void print(llvm::raw_ostream &, bool) const;
    void print(llvm::raw_ostream &, llvm::ModuleSlotTracker &, bool) const;
    void printAsOperand(llvm::raw_ostream &, bool, 
    ...

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

  parent reply	other threads:[~2022-02-18 22:07 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 [this message]
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
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-F4h5ZkMjbq@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).