public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: David Taylor <dtaylor@usendtaylorx2l.lss.emc.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: RFA bug fix -- x86-64 stabs and deprecated fp register
Date: Wed, 03 Dec 2014 03:19:00 -0000	[thread overview]
Message-ID: <20141203031854.GI4882@adacore.com> (raw)
In-Reply-To: <16828.1417452115@usendtaylorx2l>

> For current systems we have earlier this year switched to DWARF, but we
> will need to support STABS for legacy systems for a few years.

Can you say which systems? I am just curious to see what systems
out there still use stabs. Also, do you have an idea of long
you might have to continue supporting stabs (it's ok if you do not
know or do not want to say).

> As far as it being obsolete, I asked about its status in January 2013 on
> the gdb list.  My take away from that discussion was that it was not
> deprecated nor obsolete and that it was being maintained; but, that new
> development was focused on DWARF.

I think that's a fair understanding, although I don't know of any
maintainer that still uses DWARF, so maintenance is likely to
remain limited to integrating patch submissions such as yours.

-- 
Joel

  reply	other threads:[~2014-12-03  3:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 20:58 David Taylor
2014-11-30 15:20 ` Joel Brobecker
2014-11-30 18:59   ` Mark Kettenis
2014-12-01 16:42     ` David Taylor
2014-12-03  3:19       ` Joel Brobecker [this message]
2014-12-01 16:30   ` David Taylor
2014-12-03  3:50     ` Joel Brobecker
2014-12-03 17:31       ` Doug Evans
2014-12-04  3:20         ` Joel Brobecker
2014-12-05 13:38     ` Mark Kettenis
2014-12-03  3:43 ` Doug Evans

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=20141203031854.GI4882@adacore.com \
    --to=brobecker@adacore.com \
    --cc=dtaylor@usendtaylorx2l.lss.emc.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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).