From: Simon Marchi <simon.marchi@polymtl.ca>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: John Baldwin <jhb@freebsd.org>, Jim Wilson <jimw@sifive.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] RISC-V: Add osabi support.
Date: Sat, 07 Jul 2018 01:53:00 -0000 [thread overview]
Message-ID: <16706857fdc1be2a14e982b3a57eaf99@polymtl.ca> (raw)
In-Reply-To: <20180706213950.GO2675@embecosm.com>
On 2018-07-06 17:39, Andrew Burgess wrote:
> * John Baldwin <jhb@FreeBSD.org> [2018-07-05 15:25:54 -0700]:
>
>> On 7/4/18 2:11 AM, Andrew Burgess wrote:
>> > * Jim Wilson <jimw@sifive.com> [2018-07-03 17:15:18 -0700]:
>> >
>> >> This adds the osabi init call that the linux native port needs.
>> >>
>> >> gdb/
>> >> * riscv-tdep.c (riscv_gdbarch_init): Call gdbarch_init_osabi.
>> >
>> > I'm happy with this patch, but again wonder if this should be part of
>> > a sequence that adds OS support?
>>
>> I would be happy to have these bits go in actually as I will probably
>> start
>> working on FreeBSD RISC-V support in the near future (albeit using
>> QEMU as my test environment for now). Having the riscv-tdep.c changes
>> upstream will make that easier rather than either duplicating that
>> work
>> or having to temporarily pull it into my own branches.
>
> In terms of the code content of this patch (and the other one I
> commented on) I'm perfectly happy.
>
> However, I don't feel I'm qualified to give the OK to merge these
> given the original push back against merging unused code. I'd rather
> a global maintainer say yes or no.
I think this is fine. That line is kind of standard boilerplate in
gdbarch_init methods. The <arch>-tdep.c file is not really supposed to
know what osabi variants exist above it, so it's ok to call it "just in
case". It's not like we are adding one thousand lines of not-yet-used
code :).
Simon
next prev parent reply other threads:[~2018-07-07 1:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 0:16 Jim Wilson
2018-07-04 9:11 ` Andrew Burgess
2018-07-05 22:26 ` John Baldwin
2018-07-06 21:39 ` Andrew Burgess
2018-07-07 1:53 ` Simon Marchi [this message]
2018-07-16 21:51 ` Jim Wilson
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=16706857fdc1be2a14e982b3a57eaf99@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.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