diff options
author | Yao Qi <yao.qi@linaro.org> | 2016-01-18 14:29:53 +0000 |
---|---|---|
committer | Yao Qi <yao.qi@linaro.org> | 2016-01-18 14:30:23 +0000 |
commit | b27896961a641e92a642b352627208233dfeb7f1 (patch) | |
tree | 8071a6587c73ff4e5abcdb8d8fc6590a4fecbb68 /gdb/testsuite/gdb.guile | |
parent | 24f03d4ecf4af77a5f0ae4968973c3387ffeb8ae (diff) | |
download | gdb-b27896961a641e92a642b352627208233dfeb7f1.zip gdb-b27896961a641e92a642b352627208233dfeb7f1.tar.gz gdb-b27896961a641e92a642b352627208233dfeb7f1.tar.bz2 |
[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.
Diffstat (limited to 'gdb/testsuite/gdb.guile')
-rw-r--r-- | gdb/testsuite/gdb.guile/scm-section-script.c | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/gdb/testsuite/gdb.guile/scm-section-script.c b/gdb/testsuite/gdb.guile/scm-section-script.c index ddd4538..0f19613 100644 --- a/gdb/testsuite/gdb.guile/scm-section-script.c +++ b/gdb/testsuite/gdb.guile/scm-section-script.c @@ -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" \ |