Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] [8/9] Cell multi-arch: Support PPU address space access
Date: Wed, 22 Jul 2009 18:16:00 -0000	[thread overview]
Message-ID: <83ws604mf0.fsf@gnu.org> (raw)
In-Reply-To: <200907221717.n6MHHYoe014875@d12av02.megacenter.de.ibm.com>

> Date: Wed, 22 Jul 2009 19:17:34 +0200 (CEST)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
> 
> --- src.orig/gdb/doc/gdb.texinfo
> +++ src/gdb/doc/gdb.texinfo
> @@ -17505,6 +17505,16 @@ function.  The default is @code{off}.
>  @kindex show spu
>  Show whether to stop for new SPE threads.
>  
> +@item set spu auto-flush-cache @var{arg}
> +Set whether to automatically flush the software-managed cache.  When set to
> +@code{on}, @value{GDBN} will automatically cause the SPE software-managed
> +cache to be flushed whenever SPE execution stops.  This provides a consistent
> +view of PowerPC memory that is accessed via the cache.  If an application
> +does not use the software-managed cache, this option has no effect.
> +
> +@item show spu auto-flush-cache
> +Show whether to automatically flush the software-managed cache.
> +
>  @end table
>  
>  @node PowerPC
> Index: src/gdb/NEWS
> ===================================================================
> --- src.orig/gdb/NEWS
> +++ src/gdb/NEWS
> @@ -258,6 +258,11 @@ set spu stop-on-load
>  show spu stop-on-load
>    Control whether to stop for new SPE threads during Cell/B.E. debugging.
>  
> +set spu auto-flush-cache
> +show spu auto-flush-cache
> +  Control whether to automatically flush the software-managed cache
> +  during Cell/B.E. debugging.
> +
>  set sh calling-convention
>  show sh calling-convention
>    Control the calling convention used when calling SH target functions.

These parts are okay.

Thanks.


      reply	other threads:[~2009-07-22 18:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22 17:22 Ulrich Weigand
2009-07-22 18:16 ` Eli Zaretskii [this message]

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=83ws604mf0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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