Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Anton Blanchard <anton@samba.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/3] Add multiple branches to single step through atomic sequence testcase
Date: Wed, 13 Jun 2012 16:06:00 -0000	[thread overview]
Message-ID: <20120613160613.GI18729@adacore.com> (raw)
In-Reply-To: <20120606135828.0d87f888@kryten>

> Test 3 conditional branches in an atomic sequence, 2 to the same
> destination.
[...]
> 2012-06-05  Anton Blanchard  <anton@samba.org>
> 
> 	* gdb.arch/ppc64-atomic-inst.s: Add second and third branch
> 	inside atomic sequence.

I won't pretend I understand PowerPC code all that well, I only know
the basics. My only concern with this change is whether you might have
reduced the number of conditions being tested. I would have expected
this  patch to *add* more code, and associated changes in the .exp
file.  But apparently, the code update is sufficient. How does the
change work? I see two labels used twice, for instance?

Thanks.

> 
> Index: gdb/gdb/testsuite/gdb.arch/ppc64-atomic-inst.s
> ===================================================================
> --- gdb.orig/gdb/testsuite/gdb.arch/ppc64-atomic-inst.s	2012-06-06 12:59:56.697580862 +1000
> +++ gdb/gdb/testsuite/gdb.arch/ppc64-atomic-inst.s	2012-06-06 13:46:08.258410718 +1000
> @@ -10,17 +10,29 @@ gdbasm_declare main
>  1:	lwarx	5,0,4
>  	cmpwi	5,0
>  	bne	2f
> +	cmpwi	5,1
> +	beq	3f
> +	cmpwi	5,2
> +	beq	3f	/* branch to same destination */
>  	addi	5,5,1
>  	stwcx.	5,0,4
>  	bne	1b
>  
> -	std	0,0(4)
> -2:	ldarx	5,0,4
> +2:	nop
> +
> +3:	std	0,0(4)
> +1:	ldarx	5,0,4
>  	cmpdi	5,0
> -	bne	3f
> +	bne	2f
> +	cmpdi	5,1
> +	beq	3f
> +	cmpwi	5,2
> +	beq	3f	/* branch to same destination */
>  	addi	5,5,1
>  	stdcx.	5,0,4
>  	bne	1b
>  
> +2:	nop
> +
>  3:	li	3,0
>  	blr

-- 
Joel


  reply	other threads:[~2012-06-13 16:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-06  3:56 [PATCH 1/3] Fix ppc64 single step over " Anton Blanchard
2012-06-06  3:57 ` [PATCH 2/3] Support up to 3 conditional branches in an atomic sequence Anton Blanchard
2012-06-13 16:02   ` Joel Brobecker
2012-07-16  6:34     ` Anton Blanchard
2012-09-28 10:44       ` Joel Brobecker
2012-09-28 11:44       ` Pedro Alves
2012-06-06  3:58 ` [PATCH 3/3] Add multiple branches to single step through atomic sequence testcase Anton Blanchard
2012-06-13 16:06   ` Joel Brobecker [this message]
2012-07-16  6:43     ` Anton Blanchard
2012-09-28 10:44   ` Joel Brobecker
2012-06-11 19:33 ` [PATCH 1/3] Fix ppc64 single step over " Joel Brobecker
2012-06-12 12:45   ` Anton Blanchard
2012-06-12 13:06     ` Luis Gustavo
2012-06-12 13:17       ` Joel Brobecker
2012-06-12 13:28         ` Luis Gustavo
2012-06-12 16:53           ` Edjunior Barbosa Machado
2012-06-13  0:46             ` Anton Blanchard
2012-06-13 14:00               ` Edjunior Barbosa Machado
2012-06-13 15:37                 ` Joel Brobecker
2012-07-16  6:23                   ` Anton Blanchard
2012-09-26 23:21                     ` Edjunior Barbosa Machado
2012-09-27 19:03                       ` Luis Gustavo
2012-09-28 10:16                     ` Joel Brobecker
2013-07-29  7:39 Anton Blanchard
2013-07-29  7:41 ` [PATCH 3/3] Add multiple branches to single step through " Anton Blanchard
2013-08-01 15:55   ` Ulrich Weigand

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=20120613160613.GI18729@adacore.com \
    --to=brobecker@adacore.com \
    --cc=anton@samba.org \
    --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