public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] gdb: Minor cleanup in some gdb.arch/* tests Date: Fri, 23 Mar 2018 12:14:00 -0000 [thread overview] Message-ID: <066cfa988ddf88ad32b7a114f2e984a13a3848c8@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 066cfa988ddf88ad32b7a114f2e984a13a3848c8 *** Author: Andrew Burgess <andrew.burgess@embecosm.com> Branch: master Commit: 066cfa988ddf88ad32b7a114f2e984a13a3848c8 gdb: Minor cleanup in some gdb.arch/* tests A small number of tests incorrectly tried to pass -Wa,-g through to GCC as an extra compile time flag, either to gdb_compile or prepare_for_testing. The problem is that the syntax used for passing the flags was incorrect, and as a result these extra flags were being ignored. Luckily, the 'debug' flag was being passed in each case anyway, which means that the '-g' flag would already be added. Given that all these tests pass 'debug', and the invalid flag has been ignored for some time, I'm just removing the flags in this commit. I've also changed the tests from using gdb_compile to prepare_for_testing, which allows some extra code to be removed from a couple of tests scripts. There should be no change in the test results after this commit. gdb/testsuite/ChangeLog: * gdb.arch/amd64-disp-step-avx.exp: Remove unneeded assembler flag option, syntax was wrong anyway. * gdb.arch/arm-disp-step.exp: Likewise. * gdb.arch/sparc64-regs.exp: Likewise. * gdb.arch/amd64-disp-step.exp: Remove unneeded assembler flag option, syntax was wrong anyway, switch to use prepare_for_testing. * gdb.arch/i386-disp-step.exp: Likewise.
next reply other threads:[~2018-03-23 12:14 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-23 12:14 sergiodj+buildbot [this message] 2018-03-23 12:14 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-03-23 12:15 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-03-23 12:22 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-03-23 12:26 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-03-23 12:28 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2018-03-23 12:28 ` Failures on Fedora-s390x-m64, " sergiodj+buildbot 2018-03-23 12:29 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-03-23 12:44 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2018-03-23 12:52 ` *** COMPILATION FAILED *** Failures on Fedora-x86_64-w64-mingw32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-03-23 12:54 ` Failures on Fedora-i686, branch master sergiodj+buildbot 2018-03-23 12:55 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2018-03-23 13:12 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-03-23 13:39 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot 2018-03-23 14:05 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
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=066cfa988ddf88ad32b7a114f2e984a13a3848c8@gdb-build \ --to=sergiodj+buildbot@sergiodj.net \ --cc=gdb-testers@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).