public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Douglas Rupp <douglas.b.rupp@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Richard Biener <rguenther@suse.de>,
	gcc-patches@gcc.gnu.org, tgingold@free.fr
Subject: Re: [PATCH] Default Alpha/VMS to DWARF2 debugging only
Date: Fri, 10 Sep 2021 09:12:06 -0700	[thread overview]
Message-ID: <CAKtaZK86szu-+MALE8L6-LF+2Tjg92foZs-N1pEd2gQkBVtF-Q@mail.gmail.com> (raw)
In-Reply-To: <b97f1bcd-053b-9967-12e8-c408cba01c9f@gmail.com>

Dwarf2 only works with an ancient GDB. VMS style was useful because it
implemented enough to get a trace back.

But as you say it’s dead, so no basis for objection.

On Fri, Sep 10, 2021 at 6:47 AM Jeff Law <jeffreyalaw@gmail.com> wrote:

>
>
> On 9/10/2021 12:52 AM, Richard Biener via Gcc-patches wrote:
> > This changes the default debug format for Alpha/VMS to DWARF2 only,
> > skipping emission of VMS debug info which is going do be deprecated
> > for GCC 12 alongside the support for STABS.
> >
> > It looks like other flavors of VMS never used VMS_DEBUG by default
> > but only the alpha port did.
> >
> > I have no good means to test anything here, it might be that we have
> > alpha-vms specific testcases that rely on the previous default.
> >
> > OK for trunk?
> >
> > Thanks,
> > Richard.
> >
> > 2021-09-10  Richard Biener  <rguenther@suse.de>
> >
> >       * config/alpha/vms.h (PREFERRED_DEBUGGING_TYPE): Define to
> >       DWARF2_DEBUG.
> It's a dead target, so yea, go for it.  Worst case it breaks someone
> notices and we know someone still cares about alpha-vms :-)
>
> Jeff
>
>

      reply	other threads:[~2021-09-10 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10  6:52 Richard Biener
2021-09-10 13:47 ` Jeff Law
2021-09-10 16:12   ` Douglas Rupp [this message]

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=CAKtaZK86szu-+MALE8L6-LF+2Tjg92foZs-N1pEd2gQkBVtF-Q@mail.gmail.com \
    --to=douglas.b.rupp@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=rguenther@suse.de \
    --cc=tgingold@free.fr \
    /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).