Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Richard.Earnshaw@arm.com, gdb-patches@sources.redhat.com
Subject: Re: Infinite loop in make_cv_type
Date: Fri, 22 Feb 2002 10:46:00 -0000	[thread overview]
Message-ID: <200202221845.SAA06227@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Fri, 22 Feb 2002 13:38:25 EST." <20020222133825.B18410@nevyn.them.org>


drow@mvista.com said:
> This makes sense.  The 'k' means const.  810 looks to be the number
> for this type, since it's the first argument to operator=.  And the
> demangling of the current method says it takes a const ref to its own
> type (thus the ERKS_, if I remember my mangling rules correctly).

> What compiler is this?  It doesn't look like GCC; I believe GCC always
> generates type-pairs instead of type-nums.  Is this some ARM compiler
> that obeys the v3 ABI?

It's gcc-current as of about 2 days ago.  Configured for arm-netbsd 
(native).

> You might want to grab the entire stab out of the object file with
> objdump -G.

The particular stab line is coming from libstdc++.so.

> A testcase might help me sort through this a little better; I was the
> last person to grub through the cv-type stuff. 

I'll see what I can come up with.

R.



  reply	other threads:[~2002-02-22 18:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22  3:41 Richard Earnshaw
2002-02-22  7:55 ` Daniel Jacobowitz
2002-02-22  9:24   ` Michael Snyder
2002-02-22  9:41     ` Richard Earnshaw
2002-02-22 10:33     ` Daniel Jacobowitz
2002-02-22 10:22   ` Richard Earnshaw
2002-02-22 10:38     ` Daniel Jacobowitz
2002-02-22 10:46       ` Richard Earnshaw [this message]
2002-02-22 11:07         ` Richard Earnshaw
2002-02-22 11:45           ` Richard Earnshaw
2002-02-22 11:52             ` Daniel Jacobowitz

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=200202221845.SAA06227@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.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