Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@kealia.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] add DMGL_PARAMS
Date: Tue, 16 Dec 2003 17:38:00 -0000	[thread overview]
Message-ID: <yf2d6aou0gq.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <20031216171544.28E9B4B412@berman.michael-chastain.com> (Michael Elizabeth Chastain's message of "Tue, 16 Dec 2003 12:15:44 -0500 (EST)")

On Tue, 16 Dec 2003 12:15:44 -0500 (EST), mec.gnu@mindspring.com (Michael Elizabeth Chastain) said:

> Be aware that dwarf 2 and stabs+ have had differences in this area.  For
> example, when is_ctor_or_dtor in the demangler was broken, dwarf 2 was
> not affected, but stabs+ was.  So there's always a chance that I'll come
> back in a few days or a week and say "you broke stabs+"!

Good point.  I've just run the testsuite with stabs+, just to
double-check that it doesn't trigger any regressions there, either.

David Carlton
carlton@kealia.com


  reply	other threads:[~2003-12-16 17:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-16 17:15 [rfa] add DMGL_PARAMS (was: new demangler) Michael Elizabeth Chastain
2003-12-16 17:38 ` David Carlton [this message]
     [not found] <yf2he01vg6z.fsf@hawaii.kealia.com>
     [not found] ` <m3y8tdfzir.fsf@gossamer.airs.com>
     [not found]   ` <yf2d6apvfg2.fsf@hawaii.kealia.com>
     [not found]     ` <m3u141fz28.fsf@gossamer.airs.com>
     [not found]       ` <m3ptepfyxh.fsf@gossamer.airs.com>
     [not found]         ` <yf28yldvevq.fsf@hawaii.kealia.com>
     [not found]           ` <m3he01fygc.fsf@gossamer.airs.com>
     [not found]             ` <yf23cblveh7.fsf@hawaii.kealia.com>
     [not found]               ` <20031216053022.GA28127@nevyn.them.org>
2003-12-16 16:54                 ` David Carlton
2003-12-16 19:23                   ` Daniel Jacobowitz
2003-12-16 19:27                     ` [rfa] add DMGL_PARAMS David Carlton

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=yf2d6aou0gq.fsf@hawaii.kealia.com \
    --to=carlton@kealia.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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