From: Andrew Cagney <cagney@gnu.org>
To: gdb@sources.redhat.com
Subject: Post GDB 6.2, require new frame code
Date: Fri, 18 Jun 2004 19:29:00 -0000 [thread overview]
Message-ID: <40D34274.50803@gnu.org> (raw)
GDB's new frame infrastructure was introduced more than a year ago
(dwarf2-frame added May '03) and then included in the 6.0 and 6.1
releases. Since that introduction, we've seen:
alpha ARM AVR CRIS d10v FRV
PA-RISC i386 ia64 m32r m68hcll
m68k m88k mips ppc s390 sh4
sparc vax
all updated to this new framework. Unfortunately, though, we're still
left with a few architectures relying on the old framework.
We're now faced with the problem of what to do with the remaining
architectures. The choices I see are:
- continue to support the legacy framework
- convert the remaining architectures
- phase out the remaining architectures
So as to avoid the problem of this dragging on indefinitely, we need to
establish a clear schedule by which all architectures are expected to
have been updated. To that end:
- make GDB 6.2 the last release to support the legacy frame code
- in 6.2 NEWS, list unconverted architectures as about to be obsoleted
- Post 6.2 release, obsolete any remaining architectures
comments,
Andrew
next reply other threads:[~2004-06-18 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 19:29 Andrew Cagney [this message]
2004-06-21 7:06 ` Jim Blandy
2004-06-21 13:30 ` Andrew Cagney
2004-06-21 7:54 ` Michael Mueller
2004-06-21 8:44 ` Jim Blandy
2004-06-23 7:41 ` Corinna Vinschen
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=40D34274.50803@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@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