public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Fix asm in testsuite/gdb.arch/aarch64-fp.c
Date: Fri, 17 Aug 2018 10:25:00 -0000	[thread overview]
Message-ID: <2ecae92e2372102ac0fa774fce4c4c0d6f8c85f5@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 2ecae92e2372102ac0fa774fce4c4c0d6f8c85f5 ***

Author: Alan Hayward <alan.hayward@arm.com>
Branch: master
Commit: 2ecae92e2372102ac0fa774fce4c4c0d6f8c85f5

Fix asm in testsuite/gdb.arch/aarch64-fp.c

Cannot assume result of first and third ldr will go into x0.
Rewrite asm to be clearer.

gdb/testsuite/

	PR gdb/18931:
	* gdb.arch/aarch64-fp.c (main): Fix asm registers.


             reply	other threads:[~2018-08-17 10:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-17 10:25 sergiodj+buildbot [this message]
2018-08-17 10:25 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-08-17 10:34 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-08-17 10:37 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-08-17 10:40 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2018-08-17 10:52 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-08-17 10:55 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-08-17 10:59 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-08-17 11:16 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-08-17 11:23 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-08-17 11:39 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-08-23  4:40 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot

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=2ecae92e2372102ac0fa774fce4c4c0d6f8c85f5@gdb-build \
    --to=sergiodj+buildbot@sergiodj.net \
    --cc=gdb-testers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).