From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH v4 0/3] OpenRISC gdb port
Date: Sat, 21 Jan 2017 12:05:10 +0900 [thread overview]
Message-ID: <cover.1484967574.git.shorne@gmail.com> (raw)
Hello,
This is the openrisc port of GDB that has been in openrisc
repositories for a very long time. The main original author
was Jeremy Bennett as can be seen in file copyrights. Others
should also have copyright assignment in place.
This along with the sim patches are the last of what has not
made its way upstream. The patches are based on current gdb
git master branch.
I have run the testsuite and results are as follows:
# of expected passes 19283
# of unexpected failures 406
# of expected failures 29
# of known failures 57
# of unresolved testcases 2
# of untested testcases 181
# of unsupported tests 264
#/build-gdb/gdb/gdb version 7.12.50.20170120-git -nw -nx -data-directory #/build-gdb/gdb/testsuite
-Stafford
--
Changes since v3
* Updates as per Luis's comments
- comment formatting issues (period then 2 spaces)
- remove spurious newlines
- merged configure.tgt clasues to single
- Fixed typos and grammar in gdb.texinfo
- Removed copyright names from source files (in docs)
- Remove curly braces around single statement if's
- (fyi) I left the casts as I think it keeps code readable
- used XCNEW for tdep init
- Added an example XML target descriptor
* Removed newlines
Changes from v2
* Updates as per Yao's comments
- Fix copyrights, jullien embecosm, remove embecosm
- indentation to use gnu style (i.e. && and || on left)
- Fix comments to use gnu style
- Move some includes around
- Remove constant variables, replace with constants
- Remove doxygen on a few calls
- Have only 1 space between type and var name
- remove todo about 4 const
- do fix *buf checks (use buf != NULL)
- BP_MANIPULATION
- Use the builtin types for reg register functions
- or1k_iterate_over_regset_sections - remove no linux, no cores yet
* Remove unimplements pseudo register functions
* Remove spr commands as we can now get those via `info reg`
Changes from v1
* Merged or1k-tdep.[ch] changes into a single commit
* Futher fixes to change log bringing in history back to 2008
* Fix doc issue on sw_breakpoint_from_kind
Franck Jullien (1):
gdb: Add OpenRISC or1k and or1knd target support
Stafford Horne (2):
or1k: gdb: Add xml tdesc
gdb: testsuite: Add or1k l.nop inscruction
gdb/configure.tgt | 6 +
gdb/doc/gdb.texinfo | 70 +
gdb/features/Makefile | 2 +
gdb/features/or1k.c | 2280 +++++++++++++++++++++++++++++++++
gdb/features/or1k.xml | 2274 ++++++++++++++++++++++++++++++++
gdb/or1k-tdep.c | 1324 +++++++++++++++++++
gdb/or1k-tdep.h | 56 +
gdb/testsuite/gdb.base/bp-permanent.c | 2 +
8 files changed, 6014 insertions(+)
create mode 100644 gdb/features/or1k.c
create mode 100644 gdb/features/or1k.xml
create mode 100644 gdb/or1k-tdep.c
create mode 100644 gdb/or1k-tdep.h
--
2.9.3
next reply other threads:[~2017-01-21 3:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 3:05 Stafford Horne [this message]
2017-01-21 3:05 ` [OpenRISC] [PATCH v4 1/3] gdb: Add OpenRISC or1k and or1knd target support Stafford Horne
2017-01-21 3:05 ` [OpenRISC] [PATCH v4 2/3] or1k: gdb: Add xml tdesc Stafford Horne
2017-01-21 3:05 ` [OpenRISC] [PATCH v4 3/3] gdb: testsuite: Add or1k l.nop inscruction Stafford Horne
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=cover.1484967574.git.shorne@gmail.com \
--to=shorne@gmail.com \
--cc=openrisc@lists.librecores.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