From: Pedro Alves <pedro@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: gdbserver: Clear regcache if buf is NULL
Date: Sun, 17 Oct 2010 08:01:00 -0000 [thread overview]
Message-ID: <201010170901.39736.pedro@codesourcery.com> (raw)
In-Reply-To: <AANLkTimbAmqU0O4i_FLzpf915-EXNPBTo-G5w2q4yzGs@mail.gmail.com>
On Saturday 16 October 2010 23:02:27, H.J. Lu wrote:
> > Does that sound good? Or do you think keep using 0 would
> > be better in this case?
> >
>
> Values in vector registers are invalid, not unavailable. OS
> initializes them to zero when they are set the firs time in
> a program. I prefer *value not valid".
Ah, yes, agreed. Okay, that's a different state from the
"unavailable" in traceframe's (which really means the register
exists, and its value also exists, but hasn't been collected
by the tracepoint actions, so we don't know what it was).
I'll adjust my patches to keep using 0 for now in cases like
the vector case we're discussing then. Thanks!
> GDB may update vector registers before they are set by program.
> GDB sets proper bits in XSAVE area to tell OS/hardware that vector
> registers now have valid values.
--
Pedro Alves
next prev parent reply other threads:[~2010-10-17 8:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 17:44 H.J. Lu
2010-02-03 17:57 ` Daniel Jacobowitz
2010-09-29 1:54 ` Pedro Alves
2010-10-01 1:51 ` H.J. Lu
2010-10-16 20:01 ` Pedro Alves
2010-10-16 20:16 ` H.J. Lu
2010-10-16 20:49 ` Pedro Alves
2010-10-16 22:02 ` H.J. Lu
2010-10-17 8:01 ` Pedro Alves [this message]
2010-10-31 13:25 ` Mark Kettenis
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=201010170901.39736.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.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