public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Jim Wilson <jimw@sifive.com>
To: Mark Wielaard <mark@klomp.org>
Cc: elfutils-devel@sourceware.org, Karsten Merker <merker@debian.org>
Subject: Re: RISC-V support
Date: Tue, 08 Jan 2019 19:28:00 -0000	[thread overview]
Message-ID: <CAFyWVabv0EEE-8oYEe8aQb1pqeXkkKusTg4nq1eHLrKhF43_jA@mail.gmail.com> (raw)
In-Reply-To: <c78cbce53b0276468331a647d669648ed9caa05f.camel@klomp.org>

On Tue, Jan 8, 2019 at 5:52 AM Mark Wielaard <mark@klomp.org> wrote:
> The _start one seems to be:
> https://sourceware.org/bugzilla/show_bug.cgi?id=23125
> So that is fixed with glibc 2.29.
>
> Do you have a bug for the second issue with __thread_start?

https://sourceware.org/bugzilla/show_bug.cgi?id=24040

I plan to write a patch for it, if Andreas Schwab doesn't get to it
first, but the Fedora koji package server was down for a few weeks
which prevented me from installing the packages I needed to do this
work.  It is back up and I am looking at this now.

> It would be nice to have some riscv setup for our buildbot. Do you
> happen to have recommendations for something like that? Any distro that
> gets regular toolchain updates? Is a libvirt/qemu setup reliable enough
> or would you recommend trying to get real hardware?

I've been using Fedora, but Debian and OpenSuse are both usable too.
Fedora is just a little more convenient for me as they have images I
can download and boot, and a git tree for building a kernel with NBD
support which makes the HiFive Unleashed much more stable than when
using the SDcard for the root file system.  Plus I used to work for
Cygnus/Red Hat so maybe I am a little biased.

QEMU works too.  There are some known bugs in the RISC-V qemu FP
support, I wouldn't use it for numerical work.  If you stress the
system you might find some bugs, but overall it is certainly usable.
I used qemu for my gdb work, because it was easier to try kernel
patches that way, and I didn't want to risk trying untested kernel
patches on my main RISC-V development system.  The linux distro folks
are using qemu for builds also, to supplement the builds on hardware,
as they have limited numbers of boards at present.

There is only one ASIC option for running linux that I know of at this
time, and that is the SiFive HiFive Unleashed.  It is faster than qemu
running on a fast x86_64 machine.  It is stable if you don't use the
SDcard for anything other than booting.  I've hit 60 days of uptime on
my board, running a patched 4.15 kernel.  There are also FPGA options,
but these are more complicated and probably more expensive than using
the HiFive Unleashed.  I expect that more hardware options will be
available in the future.

Jim

  reply	other threads:[~2019-01-08 19:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-27  2:29 Jim Wilson
2019-01-08 13:52 ` Mark Wielaard
2019-01-08 19:28   ` Jim Wilson [this message]
2019-01-08 21:52   ` Karsten Merker
2019-01-11 23:23   ` Kurt Roeckx
2019-01-12 22:35     ` Mark Wielaard
2019-01-12 23:21       ` Kurt Roeckx
2019-01-13  1:06         ` Jim Wilson
2019-01-13  1:23           ` Kurt Roeckx
2019-01-13 22:15             ` 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=CAFyWVabv0EEE-8oYEe8aQb1pqeXkkKusTg4nq1eHLrKhF43_jA@mail.gmail.com \
    --to=jimw@sifive.com \
    --cc=elfutils-devel@sourceware.org \
    --cc=mark@klomp.org \
    --cc=merker@debian.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).