Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com
Cc: fnf@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC] const qualifiers in gdb.c++/method.exp
Date: Fri, 11 Jan 2002 05:13:00 -0000	[thread overview]
Message-ID: <200201111313.HAA32674@duracef.shout.net> (raw)

Daniel Jacobowitz wrote:
> Mind trying again?  I think Fred fixed these - or someone else did...

Okay, here's some fresh test results.  The type of "print this" in
a const method is:

  "A *"
    native i686-pc-linux-gnu, gdb HEAD, gcc 2.95.3, -gstabs+
    native i686-pc-linux-gnu, gdb HEAD, gcc 3.0.2, -gstabs+
    native i686-pc-linux-gnu, gdb HEAD, gcc HEAD, -gstabs+
    native i686-pc-linux-gnu, gdb HEAD, gcc gcc-3_0-branch, -gstabs+

  "const A * const"
    native i686-pc-linux-gnu, gdb HEAD, gcc 2.95.3, -gdwarf-2
    native i686-pc-linux-gnu, gdb HEAD, gcc 3.0.2, -gdwarf-2
    native i686-pc-linux-gnu, gdb HEAD, gcc HEAD, -gdwarf-2
    native i686-pc-linux-gnu, gdb HEAD, gcc gcc-3_0-branch, -gdwarf-2

This is an improvement from 2001-12-22, when dwarf-2 + v3 compiler
resulted in "A * const".

So over in Fred Fish's patch, I'd like to see fragment #2 look
something like this:

    get_debug_format
    setup_xfail_format stabs
    ...
    -re "\\$\[0-9\]* = \\(const A \\*( const)?\\) $hex\r\n$gdb_prompt $" {

I'd like the first const to be mandatory, with an xfail for stabs.

(My paperwork is almost done, and then I can commit my own patches
as well as approve other people's).

Michael C


             reply	other threads:[~2002-01-11 13:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-11  5:13 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-01-10  7:07 Michael Elizabeth Chastain
2002-01-10 11:59 ` Daniel Jacobowitz
2002-01-09  8:53 Michael Elizabeth Chastain
2002-01-09 10:52 ` Daniel Jacobowitz
2002-01-08  9:47 Fred Fish

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=200201111313.HAA32674@duracef.shout.net \
    --to=mec@shout.net \
    --cc=drow@mvista.com \
    --cc=fnf@redhat.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