From: Dmitry Vyukov <dvyukov@google.com>
To: David Abdurachmanov <david.abdurachmanov@gmail.com>
Cc: "Albert Ou" <aou@eecs.berkeley.edu>,
"Andreas Schwab" <schwab@suse.de>,
syzkaller <syzkaller@googlegroups.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Tobias Klauser" <tklauser@distanz.ch>,
linux-riscv <linux-riscv@lists.infradead.org>,
"Björn Töpel" <bjorn.topel@gmail.com>
Subject: Re: syzkaller on risc-v
Date: Tue, 30 Jun 2020 15:23:58 +0200 [thread overview]
Message-ID: <CACT4Y+aZ59njQqfJPKL+y9DnYu=1z8rT7Q5e0n2iWJ9w3_ojeA@mail.gmail.com> (raw)
In-Reply-To: <CAEn-LTqVR4CXk-q=7zwFKvgmHEZpP+AO0XiycKf9mDAHS60_yg@mail.gmail.com>
On Tue, Jun 30, 2020 at 3:21 PM David Abdurachmanov
<david.abdurachmanov@gmail.com> wrote:
>
> On Tue, Jun 30, 2020 at 4:07 PM Andreas Schwab <schwab@suse.de> wrote:
> >
> > On Jun 30 2020, Dmitry Vyukov wrote:
> >
> > > Maybe it's a known issue? Should we use tip instead of 1.14? Is it more stable?
> >
> > Go is still broken, it doesn't even bootstrap.
>
> Could you elaborate? I have Golang available in Fedora/RISCV and the
> bootstrap process was fine (after the TLB bug fix was applied in
> OpenSBI). The current stable release is missing cgo and buildmode pie
> support, but otherwise seems to work fine. I was told that cgo and
> buildmode pie is supported now, but not sure if that will land in the
> next release.
FWIW I took stock Go 1.14 and the whole large system mostly worked
without any problems (except for these episodic crashes).
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2020-06-30 13:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 12:48 syzkaller on risc-v Dmitry Vyukov
2020-06-30 12:57 ` Andreas Schwab
2020-06-30 13:26 ` Dmitry Vyukov
2020-06-30 13:33 ` Andreas Schwab
2020-06-30 13:40 ` Dmitry Vyukov
2020-06-30 13:45 ` Andreas Schwab
2020-06-30 13:49 ` Dmitry Vyukov
2020-06-30 13:52 ` Andreas Schwab
2020-07-01 10:42 ` Björn Töpel
2020-07-01 10:43 ` Björn Töpel
2020-07-01 11:34 ` Dmitry Vyukov
2020-07-01 13:52 ` Tobias Klauser
2020-06-30 13:03 ` Andreas Schwab
2020-06-30 13:26 ` David Abdurachmanov
2020-06-30 13:36 ` Colin Ian King
2020-06-30 13:37 ` Colin Ian King
2020-06-30 13:57 ` David Abdurachmanov
2020-06-30 14:55 ` Andreas Schwab
2020-07-06 10:12 ` Colin Ian King
2020-07-14 1:21 ` Palmer Dabbelt
2020-06-30 13:07 ` Andreas Schwab
2020-06-30 13:20 ` David Abdurachmanov
2020-06-30 13:23 ` Dmitry Vyukov [this message]
2020-06-30 13:30 ` Andreas Schwab
2020-06-30 13:35 ` David Abdurachmanov
2020-06-30 13:43 ` Andreas Schwab
2020-07-02 22:00 ` Aurelien Jarno
2020-07-06 8:14 ` Andreas Schwab
2020-06-30 15:10 ` Tobias Klauser
2020-07-01 10:03 ` Dmitry Vyukov
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='CACT4Y+aZ59njQqfJPKL+y9DnYu=1z8rT7Q5e0n2iWJ9w3_ojeA@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn.topel@gmail.com \
--cc=david.abdurachmanov@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=schwab@suse.de \
--cc=syzkaller@googlegroups.com \
--cc=tklauser@distanz.ch \
/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 NNTP newsgroup(s).