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

On Tue, Jul 25, 2017 at 12:45 PM, Steve Ellcey <sellcey@cavium.com> wrote:
>
> Following up to my own mail at
> ttps://sourceware.org/ml/gdb/2017-07/msg00037.html
>
> It looks like the problem is with the GCC compiler.  If I use
> GCC 4.8.4 to run the gdb.base/store.c test case it works,
> if I use GCC 5.4.0 it does not.  I actually get around 50 or
> more gdb failures when I use GCC 5.4.0 rather than GCC 4.8.0.
> I believe that this may be due to aarch64 changing over from
> reload to lra during this timeframe.
>
> I have also found that the test case works if I remove the
> register keywords from the test.  Apparently the register
> keyword is ignored when optimizing but not at -O0.

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)
{

....

  if (optimize)
    return true;

  if (!DECL_REGISTER (decl))
    return false;

  /* When not optimizing, disregard register keyword for types that
     could have methods, otherwise the methods won't be callable from
     the debugger.  */
  if (RECORD_OR_UNION_TYPE_P (TREE_TYPE (decl)))
    return false;

  return true;
}

--------- CUT ------

This code has been that way since 2009 (r144939) but that function
returned true for DECL_REGISTER before that.

Thanks,
Andrew Pinski


>
> Steve Ellcey
> sellcey@cavium.com


  reply	other threads:[~2017-07-25 22:13 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 [this message]
2017-07-25 22:26   ` Steve Ellcey
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='CA+=Sn1kmymF0+6BvtyKsVeXpd4SG-PkbhvPVgM94pHMpJpRJDw@mail.gmail.com' \
    --to=apinski@cavium.com \
    --cc=gdb@sourceware.org \
    --cc=sellcey@cavium.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