From: Andreas Schwab <schwab@suse.de>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: "Albert Ou" <aou@eecs.berkeley.edu>,
"Björn Töpel" <bjorn.topel@gmail.com>,
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>
Subject: Re: syzkaller on risc-v
Date: Tue, 30 Jun 2020 15:45:25 +0200 [thread overview]
Message-ID: <mvmv9j8llai.fsf@suse.de> (raw)
In-Reply-To: <CACT4Y+askdjyUjw=D6yqnOHy8n7N3h7QFs8KjvkU5DOHGY66Zg@mail.gmail.com> (Dmitry Vyukov's message of "Tue, 30 Jun 2020 15:40:18 +0200")
On Jun 30 2020, Dmitry Vyukov wrote:
> On Tue, Jun 30, 2020 at 3:33 PM Andreas Schwab <schwab@suse.de> wrote:
>>
>> On Jun 30 2020, Dmitry Vyukov wrote:
>>
>> > On Tue, Jun 30, 2020 at 3:14 PM Andreas Schwab <schwab@suse.de> wrote:
>> >>
>> >> On Jun 30 2020, Dmitry Vyukov wrote:
>> >>
>> >> > KASAN would be a prerequisite for testing risc-v on syzbot.
>> >>
>> >> You need to implement the GCC support first.
>> >
>> > Interesting. Björn claimed KASAN works already. And there is:
>> >
>> > commit 8ad8b72721d0f07fa02dbe71f901743f9c71c8e6
>> > Author: Nick Hu
>> > Date: Mon Jan 6 10:38:32 2020 -0800
>> > riscv: Add KASAN support
>> >
>> > Is there any known issue with gcc?
>>
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91441
>>
>> $ gcc -fsanitize=kernel-address -xc - </dev/null
>> cc1: warning: ‘-fsanitize=address’ and ‘-fsanitize=kernel-address’ are not supported for this target
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91441#c3
> Fixed ;)
Yes. What's your point?
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."
_______________________________________________
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:45 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 [this message]
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
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=mvmv9j8llai.fsf@suse.de \
--to=schwab@suse.de \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn.topel@gmail.com \
--cc=dvyukov@google.com \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.