From: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
To: Anton Blanchard <anton@samba.org>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com,
luis_gustavo@mentor.com
Subject: Re: [PATCH 1/3] Fix ppc64 single step over atomic sequence testcase
Date: Tue, 30 Jul 2013 17:15:00 -0000 [thread overview]
Message-ID: <51F7F4B7.7020303@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130729173838.36f370a6@kryten>
On 07/29/2013 04:38 AM, Anton Blanchard wrote:
>
> (My apologies, I thought I'd got these patches merged but obviously I
> hadn't).
>
> The current ppc64 single step over atomic sequence testcase is broken.
> Convert the test into assembly and use stepi to step through it.
Hi Anton,
thanks for reworking this patch! I do recall we discussed this in the
mailing list last year
(http://sourceware.org/ml/gdb-patches/2012-06/msg00162.html).
>
> Anton
> --
>
> 2013-07-29 Anton Blanchard <anton@samba.org>
>
> * gdb.arch/ppc64-atomic-inst.c: Remove
> * gdb.arch/ppc64-atomic-inst.s: New file
> * gdb.arch/ppc64-atomic-inst.exp: Adapt for asm based testcase
>
(just a nitpick: missing period at the end of the lines.)
> Index: gdb/gdb/testsuite/gdb.arch/ppc64-atomic-inst.exp
> ===================================================================
> --- gdb.orig/gdb/testsuite/gdb.arch/ppc64-atomic-inst.exp
> +++ gdb/gdb/testsuite/gdb.arch/ppc64-atomic-inst.exp
> @@ -27,9 +27,9 @@ if {![istarget "powerpc*"] || ![is_lp64_
> }
>
> set testfile "ppc64-atomic-inst"
> -set srcfile ${testfile}.c
> +set srcfile ${testfile}.s
> set binfile ${objdir}/${subdir}/${testfile}
> -set compile_flags {debug quiet}
> +set compile_flags "debug quiet additional_flags=-I${srcdir}/gdb.asm"
I've noticed it fails to build with the following:
spawn -ignore SIGHUP gcc ../../../gdb.git/gdb/testsuite/gdb.arch/ppc64-atomic-inst.s -I../../../gdb.git/gdb/testsuite/gdb.asm -g -lm -o /home/emachado/gdb/build/gdb/testsuite/gdb.arch/ppc64-atomic-inst^M
../../../gdb.git/gdb/testsuite/gdb.arch/ppc64-atomic-inst.s: Assembler messages:^M
../../../gdb.git/gdb/testsuite/gdb.arch/ppc64-atomic-inst.s:1: Error: can't open common.inc for reading: No such file or directory^M
../../../gdb.git/gdb/testsuite/gdb.arch/ppc64-atomic-inst.s:2: Error: can't open powerpc64.inc for reading: No such file or directory^M
../../../gdb.git/gdb/testsuite/gdb.arch/ppc64-atomic-inst.s:5: Error: Unrecognized opcode: `gdbasm_declare'^M
compiler exited with status 1
This seems to happen because -I option is not passed to the assembler. I've
tried adding this parameter using -Wa as:
set compile_flags "debug quiet additional_flags=-Wa,-I${srcdir}/gdb.asm"
and it fixes the build failure. With this change, the testcase passes OK, also
including the other 2 patches you sent on this thread.
Thanks and regards,
--
Edjunior
next prev parent reply other threads:[~2013-07-30 17:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 7:39 Anton Blanchard
2013-07-29 7:40 ` [PATCH 2/3] Support up to 3 conditional branches in an atomic sequence Anton Blanchard
2013-08-01 15:39 ` Ulrich Weigand
2013-07-29 7:41 ` [PATCH 3/3] Add multiple branches to single step through atomic sequence testcase Anton Blanchard
2013-08-01 15:55 ` Ulrich Weigand
2013-07-30 17:15 ` Edjunior Barbosa Machado [this message]
2013-07-31 12:31 ` [PATCH 1/3] Fix ppc64 single step over " Anton Blanchard
2013-08-01 15:54 ` Ulrich Weigand
2013-08-02 13:45 ` Anton Blanchard
-- strict thread matches above, loose matches on Subject: below --
2014-03-31 2:59 Anton Blanchard
2014-03-31 15:38 ` Ulrich Weigand
2012-06-06 3:56 Anton Blanchard
2012-06-11 19:33 ` 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
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=51F7F4B7.7020303@linux.vnet.ibm.com \
--to=emachado@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=luis_gustavo@mentor.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