Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Markus Deuling <deuling@de.ibm.com>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Ulrich Weigand <uweigand@de.ibm.com>
Subject: [RFA] Implement Cell BE SPU-specific vector type
Date: Wed, 13 Dec 2006 13:39:00 -0000	[thread overview]
Message-ID: <45800270.2050508@de.ibm.com> (raw)

Hello,

there were problems with whitespaces in the last patch I posted, so here 
it is again.

I reworked the patch that adds a SPU-specific vector type to spu-tdep.c 
(the order of the union fields is changed).

Ok to apply ?

ChangeLog:

     * spu-tdep.c (spu_init_vector_type): New function.
     (spu_builtin_type_vec128.): New static variable.
     (spu_register_type): Return spu_builtin_type_vec128 as default.
     (_initialize_spu_tdep): Call spu_init_vector_type.

=======================================
diff -urN src/gdb/spu-tdep.c dev/gdb/spu-tdep.c
--- src/gdb/spu-tdep.c  2006-11-22 14:49:53.000000000 +0100
+++ dev/gdb/spu-tdep.c  2006-12-12 17:05:24.000000000 +0100
@@ -45,6 +45,8 @@

  #include "spu-tdep.h"

+/* SPU-specific vector type.  */
+struct type *spu_builtin_type_vec128;

  /* Registers.  */

@@ -84,7 +86,7 @@
  spu_register_type (struct gdbarch *gdbarch, int reg_nr)
  {
    if (reg_nr < SPU_NUM_GPRS)
-    return builtin_type_vec128;
+    return spu_builtin_type_vec128;

    switch (reg_nr)
      {
@@ -1092,8 +1094,31 @@
    return gdbarch;
  }

+/* Implement a SPU-specific vector type as replacement
+   for __gdb_builtin_type_vec128.  */
+static void
+spu_init_vector_type (void)
+{
+  struct type *type;
+
+  type = init_composite_type ("__spu_builtin_type_vec128", 
TYPE_CODE_UNION);
+  append_composite_type_field (type, "uint128", builtin_type_int128);
+  append_composite_type_field (type, "v2_int64", builtin_type_v2_int64);
+  append_composite_type_field (type, "v4_int32", builtin_type_v4_int32);
+  append_composite_type_field (type, "v8_int16", builtin_type_v8_int16);
+  append_composite_type_field (type, "v16_int8", builtin_type_v16_int8);
+  append_composite_type_field (type, "v2_double", builtin_type_v2_double);
+  append_composite_type_field (type, "v4_float", builtin_type_v4_float);
+
+  TYPE_FLAGS (type) |= TYPE_FLAG_VECTOR;
+  TYPE_NAME (type) = "spu_builtin_type_vec128";
+  spu_builtin_type_vec128 = type;
+}
+
  void
  _initialize_spu_tdep (void)
  {
    register_gdbarch_init (bfd_arch_spu, spu_gdbarch_init);
+
+  spu_init_vector_type ();
  }


Regards,
Markus

-- 
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com


             reply	other threads:[~2006-12-13 13:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-13 13:39 Markus Deuling [this message]
2006-12-13 13:52 ` Ulrich Weigand
2006-12-13 14:19 ` Ulrich Weigand
  -- strict thread matches above, loose matches on Subject: below --
2006-12-12 16:13 Markus Deuling
2006-12-07 11:07 Markus Deuling

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=45800270.2050508@de.ibm.com \
    --to=deuling@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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