Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Taylor <taylor@cygnus.com>
To: Fernando Nasser <fnasser@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: Small fix to valops.c (value_assign)
Date: Mon, 12 Jun 2000 07:15:00 -0000	[thread overview]
Message-ID: <200006121414.KAA01113@texas.cygnus.com> (raw)

    Date: Fri, 09 Jun 2000 00:57:07 +0000
    From: Fernando Nasser <fnasser@cygnus.com>

    This causes some spurious register reads (sometimes to a invalid
    register number) on some targets when reading fields of typed registers
    that are not on the first byte of the register.

I assume that you mean that it *PREVENTS* some spurious register reads...
    -- 
    Fernando Nasser
    Red Hat Canada Ltd.    E-Mail:  fnasser@cygnus.com

    Index: ChangeLog
    ===================================================================
    RCS file: /cvs/src/src/gdb/ChangeLog,v
    retrieving revision 1.457
    diff -c -p -r1.457 ChangeLog
    *** ChangeLog   2000/06/09 00:51:54     1.457
    --- ChangeLog   2000/06/09 00:54:04
    ***************
    *** 1,5 ****
    --- 1,10 ----
      2000-06-08  Fernando Nasser  <fnasser@cygnus.com>

    +       * valops.c (value_assign): Adjust the length to take into
    +       consideration that we are not starting from the beginning.
    + 
    + 2000-06-08  Fernando Nasser  <fnasser@cygnus.com>
    + 
	    * values.c (value_primitive_field): Copy VALUE_REGNO as well.
	    With typed registers we may have the location information in this field,
	    in addition to VALUE_ADDRESS (which was already being copied).

Approved.

    Index: valops.c
    ===================================================================
    RCS file: /cvs/src/src/gdb/valops.c,v
    retrieving revision 1.16
    diff -c -p -r1.16 valops.c
    *** valops.c    2000/05/28 01:12:33     1.16
    --- valops.c    2000/06/09 00:54:05
    *************** value_assign (toval, fromval)
    *** 660,666 ****
	    if (VALUE_BITSIZE (toval))
	    {
	      char buffer[sizeof (LONGEST)];
    !         int len = REGISTER_RAW_SIZE (VALUE_REGNO (toval));

	      if (len > (int) sizeof (LONGEST))
		error ("Can't handle bitfields in registers larger than %d bits.",
    --- 660,667 ----
	    if (VALUE_BITSIZE (toval))
	    {
	      char buffer[sizeof (LONGEST)];
    !         int len = 
    !               REGISTER_RAW_SIZE (VALUE_REGNO (toval)) - VALUE_OFFSET (toval);

	      if (len > (int) sizeof (LONGEST))
		error ("Can't handle bitfields in registers larger than %d bits.",


             reply	other threads:[~2000-06-12  7:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-12  7:15 David Taylor [this message]
2000-06-12  7:33 ` Fernando Nasser

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=200006121414.KAA01113@texas.cygnus.com \
    --to=taylor@cygnus.com \
    --cc=fnasser@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.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