From: Tom de Vries <tdevries@suse.de>
To: Carl Love <cel@us.ibm.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
Will Schmidt <will_schmidt@vnet.ibm.com>
Subject: Re: [PATCH] PowerPC, fix gdb.base/retval-large-struct.exp
Date: Fri, 18 Nov 2022 15:46:33 +0100 [thread overview]
Message-ID: <a08df8bd-e6b7-f6c7-cf46-a5cf04c0c607@suse.de> (raw)
In-Reply-To: <71926c391f43cee2051ea0c9b449ec0aecc847ec.camel@us.ibm.com>
On 11/16/22 23:11, Carl Love via Gdb-patches wrote:
> -if {[prepare_for_testing "failed to prepare" $testfile $srcfile debug]} {
> +set additional_flags ""
> +
> +if {[have_fvar_tracking]} {
> + set additional_flags "additional_flags= -fvar-tracking"
> +}
> +
> +if {[prepare_for_testing "failed to prepare" $testfile $srcfile [list debug $additional_flags]]} {
> return -1
> }
>
AFAIU, needing -fvar-tracking is specific to powerpc, so we should limit
it's impact to that target.
And it's a gcc compiler flag, so perhaps we should limit it's impact to
that as well.
And if we indeed need it but it's not available, we should skip the test
(or xfail the failing bit), because we cannot expect it to succeed.
So how about something like this:
...
set flags {}
lappend flags debug
if { [istarget powerpc*-*-*] && [is_c_compiler_gcc] } {
if { [have_fvar_tracking] } {
lappend flags -fvar-tracking
} else {
unsupported "gcc used, -fvar-tracking needed"
return -1
}
}
if {[prepare_for_testing "failed to prepare" $testfile $srcfile $flags]} {
return -1
}
...
Thanks,
- Tom
next prev parent reply other threads:[~2022-11-18 14:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 22:11 Carl Love
2022-11-17 12:57 ` Ulrich Weigand
2022-11-17 16:18 ` Carl Love
2022-11-18 14:46 ` Tom de Vries [this message]
2022-11-18 16:04 ` Ulrich Weigand
2022-11-18 16:14 ` Carl Love
2022-11-18 16:25 ` Tom de Vries
2022-11-18 19:11 ` Carl Love
2022-11-19 6:42 ` Tom de Vries
2022-11-23 12:44 ` Ulrich Weigand
2023-03-07 18:59 ` Tom Tromey
2023-03-08 13:48 ` Ulrich Weigand
2023-03-08 15:15 ` Tom Tromey
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=a08df8bd-e6b7-f6c7-cf46-a5cf04c0c607@suse.de \
--to=tdevries@suse.de \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=cel@us.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=will_schmidt@vnet.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).