From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Rewrite GNAT-encoded fixed point types in DWARF reader
Date: Tue, 02 Mar 2021 13:08:15 -0700 [thread overview]
Message-ID: <87czwhco9c.fsf@tromey.com> (raw)
In-Reply-To: <20210210191944.2564775-1-tromey@adacore.com> (Tom Tromey's message of "Wed, 10 Feb 2021 12:19:44 -0700")
>>>>> "Tom" == Tom Tromey <tromey@adacore.com> writes:
Tom> gdb currently supports two different styles of fixed-point. The
Tom> original style, where fixed point types are "GNAT encoded", is handled
Tom> primarily in the Ada code. The newer style, encoded using DWARF, is
Tom> handled by the core of gdb.
Tom> This patch changes gdb to read the GNAT encodings in the DWARF reader
Tom> as well. This removes some code and unifies the two paths. As a
Tom> result, GNAT-encoded fixed-point now works a bit better.
Tom> One possible drawback of this change is that, if someone uses stabs,
Tom> then fixed-point might now stop working. I consider stabs to be fully
Tom> obsolete, though, so I don't intend to address this.
I'm checking this in now.
Tom
prev parent reply other threads:[~2021-03-02 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 19:19 Tom Tromey
2021-03-02 20:08 ` Tom Tromey [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=87czwhco9c.fsf@tromey.com \
--to=tromey@adacore.com \
--cc=gdb-patches@sourceware.org \
/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).