From: Daniel Jacobowitz <drow@false.org>
To: Keith Seitz <keiths@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Special casing dtors?
Date: Thu, 02 Apr 2009 16:32:00 -0000 [thread overview]
Message-ID: <20090402163148.GA29877@caradoc.them.org> (raw)
In-Reply-To: <49D4E6FE.1070506@redhat.com>
On Thu, Apr 02, 2009 at 09:25:34AM -0700, Keith Seitz wrote:
> Daniel Jacobowitz wrote:
>> On Wed, Apr 01, 2009 at 04:46:17PM -0700, Keith Seitz wrote:
>
>> I don't understand the patch - would you mind posting affected stabs
>> from 4.2 and HEAD? Sounds like GCC made the incompatible change here,
>> not GDB.
>
> Stabs attached.
>
> Gcc did make the change, but as Pedro pointed out in a previous note,
> "GDB has to cope with code produced from older compilers as well." Since
> 4.2.0 and 4.2.4 are long out the door, I was simply attempting to
> accommodating.
IIUC GCC replaced "__base_ctor" with "__base_ctor " at some point.
Assuming I've got that right, this patch is fine - please go ahead.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-04-02 16:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 22:39 Keith Seitz
2009-03-26 22:07 ` Tom Tromey
2009-03-26 22:39 ` Stan Shebs
2009-03-27 2:35 ` Daniel Jacobowitz
2009-03-27 8:07 ` Keith Seitz
2009-03-27 15:06 ` Pedro Alves
2009-03-27 15:41 ` Joel Brobecker
2009-03-27 17:19 ` Keith Seitz
2009-03-27 17:49 ` Pedro Alves
2009-03-27 19:05 ` Keith Seitz
2009-03-27 19:22 ` Pedro Alves
2009-03-28 0:56 ` Keith Seitz
2009-03-28 8:56 ` Keith Seitz
2009-03-30 21:46 ` Pedro Alves
2009-04-01 23:48 ` Keith Seitz
2009-04-02 3:17 ` Daniel Jacobowitz
2009-04-02 16:25 ` Keith Seitz
2009-04-02 16:32 ` Daniel Jacobowitz [this message]
2009-04-02 8:27 ` Mark Kettenis
2009-04-07 20:54 ` Pedro Alves
2009-04-07 21:26 ` Keith Seitz
2009-04-24 6:06 ` Tom Tromey
2009-04-24 17:54 ` Keith Seitz
2009-04-24 22:49 ` Tom Tromey
2009-06-16 18:41 ` Keith Seitz
2009-03-28 21:19 ` Tom Tromey
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=20090402163148.GA29877@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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