From: Daniel Berlin <dan@www.cgsoftware.com>
To: Jason Merrill <jason_merrill@redhat.com>
Cc: Andrew Cagney <ac131313@cygnus.com>,
Alexandre Oliva <aoliva@redhat.com>,
Jim Wilson <wilson@cygnus.com>, <gcc@gcc.gnu.org>,
<gcc-patches@gcc.gnu.org>, <gdb@sources.redhat.com>
Subject: Re: C++ ptrmemfun break if FUNCTION_BOUNDARY < 2 * BITS_PER_UNIT
Date: Wed, 16 May 2001 07:18:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0105161016220.12463-100000@www.cgsoftware.com> (raw)
In-Reply-To: <m3y9rxh8q3.fsf@prospero.cambridge.redhat.com>
On 16 May 2001, Jason Merrill wrote:
> >>>>> "Daniel" == Daniel Berlin <dan@www.cgsoftware.com> writes:
>
> > And when it comes to C++ stuf, i refuse to hard code any more stuff, after
> > just spending months cleaning up the crud from 5 years of doing that.
>
> >> Either the v3 ABI would need to specify the exact mechanism that is
> >> valid for ISA foo (i.e. GDB would would be wired to assume that all MIPS
> >> use mechanism XYZ) or the debug/object info would need to describe the
> >> mechanism being used so that GDB could adjust its self accordingly.
>
> > It's easiest to do this in debug info.
> > At least, for dwarf (I dunno how to do the same in stabs).
> > In the type die of the ptr-to-member die, just add a GCC specific
> > attribute that says which bit to check for virtuality, and i'll modify
> > gdb to handle it right (by telling the C++ ABI abstraction layer which
> > bit to check)
>
> So you'll hardcode the two possible representations, and rely on GCC to
> tell you which one to use? I suppose that's reasonable.
Well, it's much harder to do it without *some* type of gcc information.
Otherwise, we have a case of GCC knowing the real answer, and GDB having
to guess, which never ends up well. :)
>
> I'd rather put any special ABI attributes in the DW_TAG_compilation_unit,
> to avoid repetition.
This is fine too. In fact, any way you think is good to communicate it to
gdb, i'm fine with.
>
> Jason
>
next prev parent reply other threads:[~2001-05-16 7:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-06 3:14 Alexandre Oliva
2001-04-06 10:53 ` Neil Booth
2001-04-06 11:03 ` Alexandre Oliva
2001-04-07 4:52 ` Richard Earnshaw
2001-04-07 10:12 ` Dave Korn
2001-04-06 13:05 ` Jim Wilson
2001-04-06 14:45 ` DJ Delorie
2001-04-09 8:19 ` Alexandre Oliva
2001-04-09 12:28 ` Joern Rennecke
2001-04-09 13:12 ` Alexandre Oliva
2001-04-09 13:43 ` Joern Rennecke
2001-04-18 5:48 ` Richard Earnshaw
2001-04-18 12:11 ` Alexandre Oliva
2001-04-10 9:27 ` C++ ptrmemfun break if FUNCTION_BOUNDARY < 2 *BITS_PER_UNIT Mark Mitchell
2001-04-17 10:38 ` C++ ptrmemfun break if FUNCTION_BOUNDARY < 2 * BITS_PER_UNIT Andrew Cagney
2001-04-17 13:02 ` Daniel Berlin
2001-05-16 4:53 ` Jason Merrill
2001-05-16 7:18 ` Daniel Berlin [this message]
2001-04-06 3:34 dewar
2001-04-06 4:41 ` Jamie Lokier
2001-04-06 6:02 ` Joern Rennecke
2001-04-06 4:49 dewar
2001-04-06 5:00 ` Alexandre Oliva
2001-04-06 5:05 dewar
2001-04-06 5:10 ` Jamie Lokier
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=Pine.LNX.4.33.0105161016220.12463-100000@www.cgsoftware.com \
--to=dan@www.cgsoftware.com \
--cc=ac131313@cygnus.com \
--cc=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jason_merrill@redhat.com \
--cc=wilson@cygnus.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).