public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "glaubitz at physik dot fu-berlin.de" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tdep/7477] Not all floating point registers on SH4 are visible Date: Mon, 09 Feb 2015 12:50:00 -0000 [thread overview] Message-ID: <bug-7477-4717-vPGvg6eeYS@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-7477-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=7477 --- Comment #4 from glaubitz at physik dot fu-berlin.de <glaubitz at physik dot fu-berlin.de> --- Hi! (In reply to Sergio Durigan Junior from comment #3) > Thanks for your comment. Based on the Debian bug that you linked, I think > this is a matter of reviving the patch that was sent to the gdb-patches > mailing list: Yeah, I guess. I definitely want to help to get this merged into gdb and I would be happy to provide SSH access to a sh4 machine to anyone from the gdb developers interested in reviewing the patch. However, I am still waiting for my very own sh4 machine to arrive, it's currently in the mail from Japan and that might take another month or so. Once I have set everything up and working, I will ping back on the gdb mailing list and ask for another attempt. I have also a very competent gcc expert at hand who could help me reviewing the code. > You might also be interested in pinging the original author of the patch. Good idea, that's where I am going to start. Adrian -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2015-02-08 22:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-7477-4717@http.sourceware.org/bugzilla/> 2014-09-17 22:40 ` sergiodj at redhat dot com 2015-02-03 22:09 ` glaubitz at physik dot fu-berlin.de 2015-02-03 23:51 ` sergiodj at redhat dot com 2015-02-09 12:50 ` glaubitz at physik dot fu-berlin.de [this message]
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=bug-7477-4717-vPGvg6eeYS@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).