Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Steve Ellcey <sellcey@cavium.com>
To: Andrew Pinski <apinski@cavium.com>
Cc: GDB Development <gdb@sourceware.org>
Subject: Re: aarch64 gdb failures in testsuite
Date: Tue, 25 Jul 2017 22:26:00 -0000	[thread overview]
Message-ID: <1501021584.28549.89.camel@cavium.com> (raw)
In-Reply-To: <CA+=Sn1kmymF0+6BvtyKsVeXpd4SG-PkbhvPVgM94pHMpJpRJDw@mail.gmail.com>

On Tue, 2017-07-25 at 15:13 -0700, Andrew Pinski wrote:
> 
> function.c:
> /* Return true if we should assign DECL a pseudo register; false if it
>    should live on the local stack.  */
> 
> bool
> use_register_for_decl (const_tree decl)
> {
> 

Yes, I just tried tweaking that function to return false when not
optimizing, even if the decl has DECL_REGISTER set.  If fixed
gdb.base/store.exp but not much else.  The other things that did
not fail after the change were:

FAIL: gdb.base/step-over-syscall.exp: clone: displaced=off: single step over clone
FAIL: gdb.base/watchpoint.exp: next over global_ptr_ptr buffer set
FAIL: gdb.base/watchpoint.exp: next over global_ptr_ptr init
FAIL: gdb.base/watchpoint.exp: next over global_ptr_ptr pointer advance

And I don't actually see why those would change behaviour, I didn't see
any register variables in those tests  I could submit a patch to GCC
with this change but it seems like a rather large hammer to use on a
few fixes.  Maybe changing gdb.base/store.exp to not use register
variables would be a reasonable fix.  Originally, I thought that was a
bad idea because I thought the problem affected more tests, now I am
not so sure.

Steve Ellcey
sellcey@cavium.com


  reply	other threads:[~2017-07-25 22:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 19:45 Steve Ellcey
2017-07-25 22:13 ` Andrew Pinski
2017-07-25 22:26   ` Steve Ellcey [this message]
2017-07-26 17:51     ` Steve Ellcey
  -- strict thread matches above, loose matches on Subject: below --
2017-07-25 17:16 Steve Ellcey

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=1501021584.28549.89.camel@cavium.com \
    --to=sellcey@cavium.com \
    --cc=apinski@cavium.com \
    --cc=gdb@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