From: Steve Ellcey <sellcey@cavium.com>
To: gdb@sourceware.org
Subject: Re: aarch64 gdb failures in testsuite
Date: Tue, 25 Jul 2017 19:45:00 -0000 [thread overview]
Message-ID: <201707251945.v6PJjDv1022635@sellcey-dt.caveonetworks.com> (raw)
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.
Steve Ellcey
sellcey@cavium.com
next reply other threads:[~2017-07-25 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 19:45 Steve Ellcey [this message]
2017-07-25 22:13 ` Andrew Pinski
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=201707251945.v6PJjDv1022635@sellcey-dt.caveonetworks.com \
--to=sellcey@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