From: Andreas Schwab <schwab@suse.de>
To: Jim Wilson <jimw@sifive.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: contributing the RISC-V linux native port
Date: Tue, 07 Aug 2018 16:27:00 -0000 [thread overview]
Message-ID: <mvmmutyrvla.fsf@suse.de> (raw)
In-Reply-To: <CAFyWVaYJ5_FjEewyu4V2_ckpvs8RYN5REv2u9eXG7yXBSqewEw@mail.gmail.com> (Jim Wilson's message of "Tue, 7 Aug 2018 09:14:06 -0700")
On Aug 07 2018, Jim Wilson <jimw@sifive.com> wrote:
> I don't expect that my patches will cause any problems. My patch is
> improving things for me already. I've been able to use gdb to debug
> binutils, gcc, and gdb issues. But I'm a command line guy, and don't
> use any fancy gdb features, so I'm not sure how it will work for
> others.
If people find issues with it they will send patches (hopefully). A
win/win situation.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2018-08-07 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 2:22 Jim Wilson
2018-08-07 6:27 ` Palmer Dabbelt
2018-08-07 13:01 ` Joel Brobecker
2018-08-07 16:14 ` Jim Wilson
2018-08-07 16:27 ` Andreas Schwab [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=mvmmutyrvla.fsf@suse.de \
--to=schwab@suse.de \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=jimw@sifive.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