Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: deuling@de.ibm.com (Markus Deuling)
Cc: gdb-patches@sourceware.org (GDB Patches)
Subject: Re: [RFA] Implement Cell BE SPU-specific vector type
Date: Wed, 13 Dec 2006 13:52:00 -0000	[thread overview]
Message-ID: <200612131352.kBDDqHN6009841@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <45800270.2050508@de.ibm.com> from "Markus Deuling" at Dec 13, 2006 02:38:56 PM

Hi Markus,

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

I'm sorry, but this has exactly the same problems as last time ...

>      * 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.

Otherwise the patch is OK, can you either re-send with a fixed mailer
or as attachment?


Some problems:

> @@ -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)
>       {

All context lines without - or + start out with one space too many.

> +  struct type *type;
> +
> +  type = init_composite_type ("__spu_builtin_type_vec128", 
> TYPE_CODE_UNION);

Some lines are broken up ...

Maybe this
> Content-Type: text/plain; charset=ISO-8859-15; format=flowed
has something to do with the problem.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-13 13:39 Markus Deuling
2006-12-13 13:52 ` Ulrich Weigand [this message]
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=200612131352.kBDDqHN6009841@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=deuling@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    /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