public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: gcc@gcc.gnu.org, gdb@sourceware.org,
	Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: [RFC] DW_OP_piece vs. DW_OP_bit_piece on a Register
Date: Sat, 16 Jan 2016 13:27:00 -0000	[thread overview]
Message-ID: <20160116132653.GF4027@adacore.com> (raw)
In-Reply-To: <m3vb6wm86q.fsf@oc1027705133.ibm.com>

> After analyzing some test case failures in GCC and GDB I realized that
> there are various problems with the handling of DWARF pieces
> (particularly from registers) in the current implementations of GCC and
> GDB.  I'm working on a fix for the GDB part, but first I'd like to check
> whether I'm heading into the right direction -- or what the right
> direction is supposed to be.  The article below outlines these issues
> and the suggested solution options.

This is a very nice and detailed analysis of the current situation.
Thank You!

I admit that I read through the document fairly rapidly; it does
seem to me, at this point, that the first step might be to get
clarification from the DWARF committee? Or is input from the GCC/GDB
community going to help the discussion with the DWARF committee?

-- 
Joel

  reply	other threads:[~2016-01-16 13:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14 16:34 Andreas Arnez
2016-01-16 13:27 ` Joel Brobecker [this message]
2016-01-18 16:00   ` Andreas Arnez
2016-01-25 22:01 ` Matthew Fortune
2016-01-26 11:57   ` Andreas Arnez
2016-02-11 12:18     ` Matthew Fortune
2016-02-11 17:04       ` Andreas Arnez

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=20160116132653.GF4027@adacore.com \
    --to=brobecker@adacore.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=uweigand@de.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).