From: Jim Wilson <jim.wilson@linaro.org>
To: Nick Clifton <nickc@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] fix for aarch64 sim tbnz bug
Date: Mon, 12 Dec 2016 18:38:00 -0000 [thread overview]
Message-ID: <CABXYE2Xb_YNsbTGXccdbyegBNdenc_bJha3yNdiFj4cYZQy77Q@mail.gmail.com> (raw)
In-Reply-To: <CABXYE2WEVB=Bt=+uX7Sx6a9ZE4etGwFODLKnyeOzW52P+Rhe3w@mail.gmail.com>
ping
https://sourceware.org/ml/gdb-patches/2016-12/msg00128.html
On Sun, Dec 4, 2016 at 7:43 PM, Jim Wilson <jim.wilson@linaro.org> wrote:
> On Fri, Dec 2, 2016 at 1:31 AM, Mike Frysinger <vapier@gentoo.org> wrote:
>> can we please start getting tests added to sim too ? using gcc
>> indirectly to validate the sim is a bit un
>
> The GCC testsuite is the part that I care most about, but it does make
> sense for me to be adding simulator tests. There are currently no
> interesting aarch64 tests, so it isn't clear if there is any
> particular style I should be using. So I just chose a style that
> seemed OK to me. I have tests for the last two simulator patches I
> contributed. I verified that the tests work with current sources and
> fail without my two patches.
>
> I had to make a few fixes to the existing testsuite.inc file. I moved
> .Lpass and .Lfail out of the pass and fail macros, as otherwise I end
> up with duplicate definitions. I also changed fail to return
> non-zero, because it should. I find it confusing to manually run a
> testcase and see it print fail, and then return a zero exit code.
>
> Jim
>
> PS set_flags_for_add64 is broken, which causes adds and cmn to fail.
> I have a fix, and this will be my next aarch64 sim patch, but I
> haven't written a testcase yet.
next prev parent reply other threads:[~2016-12-12 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 4:49 Jim Wilson
2016-12-02 9:32 ` Mike Frysinger
2016-12-05 3:45 ` Jim Wilson
2016-12-12 18:38 ` Jim Wilson [this message]
2016-12-12 18:42 ` Mike Frysinger
2016-12-13 0:33 ` Jim Wilson
2016-12-13 6:38 ` Mike Frysinger
2016-12-13 10:45 ` Nick Clifton
2016-12-02 12:03 ` Nick Clifton
2016-12-02 15:59 ` Jim Wilson
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=CABXYE2Xb_YNsbTGXccdbyegBNdenc_bJha3yNdiFj4cYZQy77Q@mail.gmail.com \
--to=jim.wilson@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=nickc@redhat.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