From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: GDB Development <gdb@sourceware.org>, Tom Tromey <tom@tromey.com>
Subject: Re: Should a DW_OP_implicit_value be taken from the left end?
Date: Sun, 01 Jan 2017 20:13:00 -0000 [thread overview]
Message-ID: <20170101201257.GA11122@host1.jankratochvil.net> (raw)
In-Reply-To: <m3d1gi5x1t.fsf@oc1027705133.ibm.com>
On Fri, 23 Dec 2016 19:18:22 +0100, Andreas Arnez wrote:
> Right, that's another issue. If we revert the change for
> DW_OP_implicit_value, it doesn't matter anymore,
After checking your provided example I agree my patch was wrong.
I agree that DW_OP_implicit_value should be correct after reverting my patch.
> but the same bug occurs
> with DW_OP_stack_value as well. I'll handle that separately.
Yes, DW_OP_stack_value I probably fixed for my specific testcase accidentally.
It needs some different fix than the fix by me. I am fine/prefer to even
revert that part assuming you apply some correct/new fix afterwards instead.
> Note that I don't intend to revert the whole patch, only the part
> affecting DW_OP_implicit_value (DWARF_VALUE_LITERAL).
I am fine with either way, reverting just DWARF_VALUE_LITERAL or both.
> Is there any any other information about the rationale of that change?
I do everything based on real execution results and my fix (accidentally)
fixed the entry-values testcase for me on big-endian.
Thanks,
Jan
prev parent reply other threads:[~2017-01-01 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 19:42 Andreas Arnez
2016-12-21 21:39 ` Jan Kratochvil
2016-12-23 18:18 ` Andreas Arnez
2017-01-01 20:13 ` Jan Kratochvil [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=20170101201257.GA11122@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=gdb@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