Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] Fix stepping bug associated with non-contiguous blocks
Date: Mon, 15 Jul 2019 21:53:00 -0000	[thread overview]
Message-ID: <20190715145350.6ad694e0@f29-4.lan> (raw)
In-Reply-To: <20190715141116.6d240805@f29-4.lan>

On Mon, 15 Jul 2019 14:11:16 -0700
Kevin Buettner <kevinb@redhat.com> wrote:

> Do we still care about the VAX target?

After spending a few minutes looking at things, I now have an
opinion...

VAX is, historically, a very important target.  For a long time (and
perhaps even now), it was considered to be the canonical example of a
CISC architecture.

Support still exists in GCC, though it's not clear to me if it
actually works.  I saw recent patches (from April, 2019) from someone
who is trying to get VAX support in GCC to work again.

Given that GCC still has code which provides VAX architecture
support, I think that GDB should do likewise.  I think that we
should attempt to not break it (anymore than it's already broken?),
but I also don't think we should attempt to test it beyond making
sure that it still builds.

Kevin


  reply	other threads:[~2019-07-15 21:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-14  0:01 Kevin Buettner
2019-07-15 15:21 ` Tom Tromey
2019-07-15 21:11   ` Kevin Buettner
2019-07-15 21:53     ` Kevin Buettner [this message]
2019-07-18 13:36       ` Tom Tromey
2019-07-27 20:49 ` Kevin Buettner

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=20190715145350.6ad694e0@f29-4.lan \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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