Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jackie Smith Cashion <jsmith@redhat.com>
To: GDB Patches <gdb-patches@sources.redhat.com>
Subject: RFA: d10v sizeof (long long)
Date: Mon, 03 Dec 2001 17:41:00 -0000	[thread overview]
Message-ID: <3C0C1A14.58B9D2E9@redhat.com> (raw)

The following patch changes the size of the d10v long long from 4 to 8
to agree with the d10v gcc.


2001-12-03  Jackie Smith Cashion  <jsmith@redhat.com>

	* d10v-tdep.c (d10v_gdbarch_init): Change size of long long to 8 bytes.


*** d10v-tdep.c.orig	Mon Dec  3 18:26:23 2001
--- d10v-tdep.c	Mon Dec  3 18:26:29 2001
*************** d10v_gdbarch_init (struct gdbarch_info i
*** 1524,1530 ****
    set_gdbarch_short_bit (gdbarch, 2 * TARGET_CHAR_BIT);
    set_gdbarch_int_bit (gdbarch, 2 * TARGET_CHAR_BIT);
    set_gdbarch_long_bit (gdbarch, 4 * TARGET_CHAR_BIT);
!   set_gdbarch_long_long_bit (gdbarch, 4 * TARGET_CHAR_BIT);
    /* NOTE: The d10v as a 32 bit ``float'' and ``double''. ``long
       double'' is 64 bits. */
    set_gdbarch_float_bit (gdbarch, 4 * TARGET_CHAR_BIT);
--- 1524,1530 ----
    set_gdbarch_short_bit (gdbarch, 2 * TARGET_CHAR_BIT);
    set_gdbarch_int_bit (gdbarch, 2 * TARGET_CHAR_BIT);
    set_gdbarch_long_bit (gdbarch, 4 * TARGET_CHAR_BIT);
!   set_gdbarch_long_long_bit (gdbarch, 8 * TARGET_CHAR_BIT);
    /* NOTE: The d10v as a 32 bit ``float'' and ``double''. ``long
       double'' is 64 bits. */
    set_gdbarch_float_bit (gdbarch, 4 * TARGET_CHAR_BIT);


             reply	other threads:[~2001-12-04  1:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03 17:41 Jackie Smith Cashion [this message]
2001-12-03 19:30 ` Jim Blandy
2001-12-03 19:32 ` Jim Blandy
2001-12-03 19:39   ` Jackie Smith Cashion

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=3C0C1A14.58B9D2E9@redhat.com \
    --to=jsmith@redhat.com \
    --cc=gdb-patches@sources.redhat.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