Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb: Minor cleanup in some gdb.arch/* tests
Date: Thu, 22 Mar 2018 13:51:00 -0000	[thread overview]
Message-ID: <4b5623c7-72b0-4640-ce94-35be198b718d@redhat.com> (raw)
In-Reply-To: <e07d3806010beef5c6f1a7a0ad97229e726ec174.1521722330.git.andrew.burgess@embecosm.com>

On 03/22/2018 12:57 PM, Andrew Burgess wrote:
> 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.
> 
> There were two mistakes, first, the 'debug' flag was already being
> passed, this will cause GCC to add a suitable -g flag, which should
> then be propagated to the assembler.  Secondly, in order to pass
> additional compiler flags, the syntax would be
> 'additional_flags=-Wa,-g'.  As it was, the flag was just being
> ignored.
> 
> 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.
> 
> There should be no change in the test results after this commit.

OK.

> -
>  if { [prepare_for_testing "failed to prepare" ${testfile} ${srcfile} \
> -	  [list debug $additional_flags]] } {
> +	  [list debug]] } {
>      return -1

Note you could make these {debug} instead now.  "[list ...]" was only
necessary because of variable expansion.  (Don't know whether that
shortens the lines enough to avoid wrapping).  Actually, "debug" is
the default, so you could just remove them completely:

  proc prepare_for_testing { testname executable {sources ""} {options {debug}}} {

Thanks,
Pedro Alves


  reply	other threads:[~2018-03-22 13:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-22 12:57 [PATCH 0/2] Test fix in " Andrew Burgess
2018-03-22 12:57 ` [PATCH 1/2] gdb: Minor cleanup in some " Andrew Burgess
2018-03-22 13:51   ` Pedro Alves [this message]
2018-03-22 22:59     ` Andrew Burgess
2018-03-23 10:13       ` Pedro Alves
2018-03-22 12:57 ` [PATCH 2/2] gdb: Fix testsuite issue in gdb.arch/amd64-disp-step-avx.exp Andrew Burgess
2018-03-22 13:44   ` Pedro Alves
2018-03-22 23:01     ` Andrew Burgess
2018-03-23 10:13       ` Pedro Alves

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=4b5623c7-72b0-4640-ce94-35be198b718d@redhat.com \
    --to=palves@redhat.com \
    --cc=andrew.burgess@embecosm.com \
    --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