Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	"cel@us.ibm.com" <cel@us.ibm.com>
Cc: "will_schmidt@vnet.ibm.com" <will_schmidt@vnet.ibm.com>
Subject: Re: [PATCH] PowerPC, fix gdb.base/retval-large-struct.exp
Date: Fri, 18 Nov 2022 17:25:13 +0100	[thread overview]
Message-ID: <0eff963d-4633-7bdf-39be-003b1671432e@suse.de> (raw)
In-Reply-To: <fedd606083102c4b3a597ee225aa4f8d9825337d.camel@de.ibm.com>

On 11/18/22 17:04, Ulrich Weigand wrote:
> Tom de Vries <tdevries@suse.de> wrote:
> 
>> 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.
> 
> No, it's not really powerpc specific - the same mechanism can be
> used on many other platforms with an ABI that uses a return buffer
> address that is not preserved.  (E.g. we're currently looking into
> enabling it on s390x.)
> 

Right, so we can add those archs to the list of archs requiring 
-fvar-tracking support when gcc is used.

> And given that the flag is harmless if it's available (which the
> test verifies), I think it makes sense to just always enable it.
> 

That's fine by me.

Then I get:
...
set flags {}

lappend flags debug

if { [have_fvar_tracking] } {
     lappend flags -fvar-tracking
} else {
     if { ( [istarget powerpc*-*-*] || [istarget s390x*-*-* ])
          && [is_c_compiler_gcc] } {
         unsupported "gcc used, -fvar-tracking needed"
         return -1
     }
}

if {[prepare_for_testing "failed to prepare" $testfile $srcfile $flags]} {
        return -1
}
...

Thanks,
- Tom

  parent reply	other threads:[~2022-11-18 16:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 22:11 Carl Love via Gdb-patches
2022-11-17 12:57 ` Ulrich Weigand via Gdb-patches
2022-11-17 16:18   ` Carl Love via Gdb-patches
2022-11-18 14:46 ` Tom de Vries via Gdb-patches
2022-11-18 16:04   ` Ulrich Weigand via Gdb-patches
2022-11-18 16:14     ` Carl Love via Gdb-patches
2022-11-18 16:25     ` Tom de Vries via Gdb-patches [this message]
2022-11-18 19:11       ` Carl Love via Gdb-patches
2022-11-19  6:42         ` Tom de Vries via Gdb-patches
2022-11-23 12:44           ` Ulrich Weigand via Gdb-patches
2023-03-07 18:59     ` Tom Tromey via Gdb-patches
2023-03-08 13:48       ` Ulrich Weigand via Gdb-patches
2023-03-08 15:15         ` Tom Tromey via Gdb-patches

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=0eff963d-4633-7bdf-39be-003b1671432e@suse.de \
    --to=gdb-patches@sourceware.org \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=cel@us.ibm.com \
    --cc=tdevries@suse.de \
    --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