From: Doug Evans <dje@google.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org
Subject: Re: store.exp failure on i686-linux with newer gcc's
Date: Thu, 03 Sep 2009 22:17:00 -0000 [thread overview]
Message-ID: <e394668d0909031517m59f957c3l30f20291d4f352f0@mail.gmail.com> (raw)
In-Reply-To: <200909032303.56901.pedro@codesourcery.com>
On Thu, Sep 3, 2009 at 3:03 PM, Pedro Alves<pedro@codesourcery.com> wrote:
> On Thursday 03 September 2009 22:50:13, Doug Evans wrote:
>
>> Newer gcc's can store a 64 bit int in non-contiguous registers and use
>> DW_OP_piece to mark each piece.
>>
>> value->lval is set to not_lval and value_assign doesn't like that so
>> gdb refuses to set the variable with "Left operand of assignment is
>> not an lvalue."
>>
>> It seems like we need to not mark the value as not_lval and teach the
>> relevant pieces how to handle such values.
>> Anyone thought about how they want this done?
>
> Nathan Froyd has a patch for this, using the lval_computed
> machinery.
Good thing I checked first. :-)
Thanks.
What's the status? [if I may ask - no rush, just curious]
next prev parent reply other threads:[~2009-09-03 22:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 21:50 Doug Evans
2009-09-03 21:58 ` Joel Brobecker
2009-09-03 22:04 ` Pedro Alves
2009-09-03 22:17 ` Doug Evans [this message]
2009-09-03 23:44 ` Nathan Froyd
2009-09-04 16:05 ` Tom Tromey
2009-09-04 17:49 ` Nathan Froyd
2009-09-04 18:38 ` Tom Tromey
2009-09-04 20:17 ` Nathan Froyd
2009-09-04 20:18 ` Doug Evans
2009-09-04 21:23 ` Tom Tromey
2009-09-04 21:28 ` Daniel Jacobowitz
2009-09-04 22:28 ` Tom Tromey
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=e394668d0909031517m59f957c3l30f20291d4f352f0@mail.gmail.com \
--to=dje@google.com \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.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