From: Bruno Larsen <blarsen@redhat.com>
To: Tom Tromey <tom@tromey.com>,
Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v4] gdb/c++: Detect ambiguous variables in imported namespaces
Date: Fri, 6 Jan 2023 10:53:18 +0100 [thread overview]
Message-ID: <bc7ec062-452b-adb3-08b7-bb46f464531e@redhat.com> (raw)
In-Reply-To: <871qo8ep1d.fsf@tromey.com>
On 05/01/2023 20:53, Tom Tromey wrote:
>>>>>> "Bruno" == Bruno Larsen via Gdb-patches <gdb-patches@sourceware.org> writes:
> Bruno> When running gdb.cp/nsusing.cc and stopping at line 17, we can ask GDB
> Bruno> to print x and get a compiler-dependent answer. Using gcc 12.2.1, GDB
> Bruno> will print M::x, and using clang 16.0.0 prints N::x. Not only is this
> Bruno> behavior confusing to users, it is also not consistent with compiler
> Bruno> behaviors, which would warn that using x is ambiguous at this point.
>
> Thank you. This is ok.
Thanks, pushed!
> Tom
>
--
Cheers,
Bruno
prev parent reply other threads:[~2023-01-06 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 16:12 Bruno Larsen
2023-01-05 7:59 ` [PING][PATCH " Bruno Larsen
2023-01-05 19:53 ` [PATCH " Tom Tromey
2023-01-06 9:53 ` Bruno Larsen [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=bc7ec062-452b-adb3-08b7-bb46f464531e@redhat.com \
--to=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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).