OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

[testsuite] @progbits -> %progbits 

The ARM assembler has "@" as a comment character, so there are compile
errors in {py,scm}-section-script.c,

 gdb compile failed, /tmp/ccHEzYqy.s: Assembler messages:
 /tmp/ccHEzYqy.s:19: Error: junk at end of line, first unrecognized character is `,'
 /tmp/ccHEzYqy.s:24: Error: junk at end of line, first unrecognized character is `,'
 /tmp/ccHEzYqy.s:29: Error: junk at end of line, first unrecognized character is `,'
 /tmp/ccHEzYqy.s:41: Error: junk at end of line, first unrecognized character is `,'

This patch replaces @progbits with %progbits.

gdb/testsuite:

2016-01-18  Yao Qi  <yao.qi@linaro.org>

	* gdb.guile/scm-section-script.c: Replace @progbits with
	%progbits.
	* gdb.python/py-section-script.c: Likewise.
This commit is contained in:
Yao Qi 2016-01-18 14:29:53 +00:00
parent 24f03d4ecf
commit b27896961a
3 changed files with 14 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
gdb/testsuite/ChangeLog
View File

@ -1,3 +1,9 @@
2016-01-18 Yao Qi <yao.qi@linaro.org>
* gdb.guile/scm-section-script.c: Replace @progbits with
%progbits.
* gdb.python/py-section-script.c: Likewise.
2016-01-15 Pedro Alves <palves@redhat.com>
* gdb.multi/tids.exp: Test star wildcard ranges.

8
gdb/testsuite/gdb.guile/scm-section-script.c
View File

@ -21,12 +21,12 @@
/* Put the path to the pretty-printer script in .debug_gdb_scripts so
gdb will automagically loaded it.
Normally "MS" would appear here, as in
.pushsection ".debug_gdb_scripts", "MS",@progbits,1
.pushsection ".debug_gdb_scripts", "MS",%progbits,1
but we remove it to test files appearing twice in the section. */
#define DEFINE_GDB_SCRIPT(script_name) \
asm("\
.pushsection \".debug_gdb_scripts\", \"S\",@progbits\n\
.pushsection \".debug_gdb_scripts\", \"S\",%progbits\n\
.byte " XSTRING (SECTION_SCRIPT_ID_SCHEME_FILE) "\n\
.asciz \"" script_name "\"\n\
.popsection \n\
@ -43,12 +43,12 @@ DEFINE_GDB_SCRIPT (SCRIPT_FILE)
/* Inlined scripts are harder to create in the same way as
DEFINE_GDB_SCRIPT_FILE. Keep things simple and just define it here.
Normally "MS" would appear here, as in
.pushsection ".debug_gdb_scripts", "MS",@progbits,1
.pushsection ".debug_gdb_scripts", "MS",%progbits,1
but we remove it to test scripts appearing twice in the section. */
#define DEFINE_GDB_SCRIPT_TEXT \
asm( \
".pushsection \".debug_gdb_scripts\", \"S\",@progbits\n" \
".pushsection \".debug_gdb_scripts\", \"S\",%progbits\n" \
".byte " XSTRING (SECTION_SCRIPT_ID_SCHEME_TEXT) "\n" \
".ascii \"gdb.inlined-script\\n\"\n" \
".ascii \"(define test-cmd\\n\"\n" \

8
gdb/testsuite/gdb.python/py-section-script.c
View File

@ -21,12 +21,12 @@
/* Put the path to the pretty-printer script in .debug_gdb_scripts so
gdb will automagically loaded it.
Normally "MS" would appear here, as in
.pushsection ".debug_gdb_scripts", "MS",@progbits,1
.pushsection ".debug_gdb_scripts", "MS",%progbits,1
but we remove it to test files appearing twice in the section. */
#define DEFINE_GDB_SCRIPT_FILE(script_name) \
asm("\
.pushsection \".debug_gdb_scripts\", \"S\",@progbits\n\
.pushsection \".debug_gdb_scripts\", \"S\",%progbits\n\
.byte " XSTRING (SECTION_SCRIPT_ID_PYTHON_FILE) "\n\
.asciz \"" script_name "\"\n\
.popsection\n\
@ -43,12 +43,12 @@ DEFINE_GDB_SCRIPT_FILE (SCRIPT_FILE)
/* Inlined scripts are harder to create in the same way as
DEFINE_GDB_SCRIPT_FILE. Keep things simple and just define it here.
Normally "MS" would appear here, as in
.pushsection ".debug_gdb_scripts", "MS",@progbits,1
.pushsection ".debug_gdb_scripts", "MS",%progbits,1
but we remove it to test scripts appearing twice in the section. */
#define DEFINE_GDB_SCRIPT_TEXT \
asm( \
".pushsection \".debug_gdb_scripts\", \"S\",@progbits\n" \
".pushsection \".debug_gdb_scripts\", \"S\",%progbits\n" \
".byte " XSTRING (SECTION_SCRIPT_ID_PYTHON_TEXT) "\n" \
".ascii \"gdb.inlined-script\\n\"\n" \
".ascii \"class test_cmd (gdb.Command):\\n\"\n" \