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] gdb: Initial baremetal riscv support Date: Tue, 06 Mar 2018 11:15:00 -0000 [thread overview] Message-ID: <dbbb1059e62e9fed10b429c030f76f782cbc1fc4@gdb-build> (raw) *** TEST RESULTS FOR COMMIT dbbb1059e62e9fed10b429c030f76f782cbc1fc4 *** Author: Andrew Burgess <andrew.burgess@embecosm.com> Branch: master Commit: dbbb1059e62e9fed10b429c030f76f782cbc1fc4 gdb: Initial baremetal riscv support This commit introduces basic support for baremetal RiscV as a GDB target. This target is currently only tested against the RiscV software simulator, which is not included as part of this commit. The target has been tested against the following RiscV variants: rv32im, rv32imc, rv32imf, rv32imfc, rv64im, rv64imc, rv64imfd, rv64imfdc. Across these variants we pass on average 34858 tests, and fail 272 tests, which is ~0.8%. The RiscV has a feature of its ABI where structures with a single floating point field, a single complex float field, or one float and one integer field are treated differently for argument passing. The new test gdb.base/infcall-nested-structs.exp is added to cover this feature. As passing these structures should work on all targets then I've made the test as a generic one, even though, for most targets, there's probably nothing special about any of these cases. gdb/ChangeLog: * Makefile.in (ALL_TARGET_OBS): Add riscv-tdep.o (HFILES_NO_SRCDIR): Add riscv-tdep.h. (ALLDEPFILES): Add riscv-tdep.c * configure.tgt: Add riscv support. * riscv-tdep.c: New file. * riscv-tdep.h: New file. * NEWS: Mention new target. * MAINTAINERS: Add entry for riscv. gdb/testsuite/ChangeLog: * gdb.base/infcall-nested-structs.exp: New file. * gdb.base/infcall-nested-structs.c: New file. * gdb.base/float.exp: Add riscv support.
next reply other threads:[~2018-03-06 11:15 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-06 11:15 sergiodj+buildbot [this message] 2018-03-06 11:15 ` *** COMPILATION FAILED *** Failures on Fedora-i686, branch master *** BREAKAGE *** sergiodj+buildbot 2018-03-06 11:16 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2018-03-06 11:29 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-03-06 11:31 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-03-06 11:38 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-03-06 11:42 ` *** COMPILATION FAILED *** Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-03-06 11:43 ` Failures on Debian-s390x-native-gdbserver-m64, branch master sergiodj+buildbot 2018-03-06 11:45 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-03-06 11:49 ` *** COMPILATION FAILED *** Failures on Ubuntu-AArch32-native-gdbserver-m32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-03-06 11:53 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, branch master sergiodj+buildbot 2018-03-06 11:56 ` *** COMPILATION FAILED *** Failures on Ubuntu-AArch32-m32, branch master *** BREAKAGE *** sergiodj+buildbot 2018-03-07 10:40 ` Failures on Ubuntu-AArch64-m64, branch master 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=dbbb1059e62e9fed10b429c030f76f782cbc1fc4@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: linkBe 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).