From: Nelson Chu <nelson.chu@sifive.com>
To: Jim Wilson <jimw@sifive.com>
Cc: Simon Cook <simon.cook@embecosm.com>, Binutils <binutils@sourceware.org>
Subject: Re: [PATCH][GAS] RISC-V: Fix missing initialization of riscv_csr_extra structs
Date: Thu, 28 May 2020 09:01:53 +0800 [thread overview]
Message-ID: <CAJYME4FJCbZqEYdcRNpXBJZKoY9t5OmC4sj7ZB+O5V+iJQ9wcg@mail.gmail.com> (raw)
In-Reply-To: <CAFyWVaasBk6x-Qh6PrsWaor9Xbtu7ggBA8Hpx4rq0vWqNFVP_w@mail.gmail.com>
On Thu, May 28, 2020 at 7:49 AM Jim Wilson <jimw@sifive.com> wrote:
>
> On Wed, May 27, 2020 at 9:35 AM Simon Cook <simon.cook@embecosm.com> wrote:
> > The next pointer of struct riscv_csr_extra was not always initilized
> > to NULL or a valid pointer, causing the assembler to attempt to read
> > through an uninitialized pointer on startup.
>
> Thanks. Committed.
>
> Jim
Thanks :)
Nelson
prev parent reply other threads:[~2020-05-28 1:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 16:34 Simon Cook
2020-05-27 23:49 ` Jim Wilson
2020-05-28 1:01 ` Nelson Chu [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=CAJYME4FJCbZqEYdcRNpXBJZKoY9t5OmC4sj7ZB+O5V+iJQ9wcg@mail.gmail.com \
--to=nelson.chu@sifive.com \
--cc=binutils@sourceware.org \
--cc=jimw@sifive.com \
--cc=simon.cook@embecosm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).