From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org,
Jan Kratochvil <jan.kratochvil@redhat.com>,
Ken Werner <ken@linux.vnet.ibm.com>
Subject: Re: [patch] const array types
Date: Fri, 24 Sep 2010 23:00:00 -0000 [thread overview]
Message-ID: <20100924161432.GG3007@adacore.com> (raw)
In-Reply-To: <201009241638.27072.pedro@codesourcery.com>
> I disagree:
I certainly understimated the consequences of this little distinction
(I haven't used C++ 1994 or 1995)!
> It looks sane to me to not emit a whole new struct type based on
> struct S that includes a `const inst x' just for `b' (rather than
> DW_TAG_const_type pointing at struct S). Is `a' really any different?
I see you point. Perhaps this should be clarified at the DWARF level
as well?
> E.g., out of the blue, in C++ it can make the user call the
> wrong function from gdb, when there are overloads
> involved (, or templates, I guess):
Ugh!
--
Joel
next prev parent reply other threads:[~2010-09-24 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 19:32 Ken Werner
2010-09-24 4:50 ` Jan Kratochvil
2010-09-24 15:38 ` Jan Kratochvil
2010-09-24 16:27 ` Joel Brobecker
2010-09-24 16:40 ` Pedro Alves
2010-09-24 23:00 ` Joel Brobecker [this message]
2010-09-24 18:36 ` Ken Werner
2010-10-05 18:25 ` Ulrich Weigand
2010-10-05 18:43 ` Joel Brobecker
2010-10-06 15:38 ` Ken Werner
2010-10-06 15:55 ` Ulrich Weigand
2010-10-06 16:18 ` Ken Werner
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=20100924161432.GG3007@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=ken@linux.vnet.ibm.com \
--cc=pedro@codesourcery.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).