All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Michael Clark <mjc@sifive.com>
Cc: Richard Henderson <richard.henderson@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Apparently fpu/softfloat.c:1374 is reachable
Date: Fri, 9 Mar 2018 10:44:47 +0000	[thread overview]
Message-ID: <CAFEAcA_rPkjEgNc=uyQ2C+at8Zs28YZVAkOLAZk17JaVyjxuNw@mail.gmail.com> (raw)
In-Reply-To: <CAHNT7NtB16m=Sn7bWugeOOiqVyeCT4Z7VrXijMDVZBA+tUdgPw@mail.gmail.com>

On 9 March 2018 at 04:22, Michael Clark <mjc@sifive.com> wrote:
> I need to dig into this. I'll need to take the assertions out, or run with
> tracing to see which fcvt test is triggering this unreachable piece of
> code. FYI. I can look into it.

> ERROR:/Users/mclark/src/sifive/riscv-qemu/fpu/softfloat.c:1374:round_to_int_and_pack:
> code should not be reached
> qemu-images/run-tests.sh: line 6: 58437 Abort trap: 6           ${QEMU}
> -nographic -machine spike_v1.10 -kernel $i

This looks like maybe it's the issue Richard Jones sent a patch for ?
https://lists.gnu.org/archive/html/qemu-devel/2018-03/msg01005.html

thanks
-- PMM

  reply	other threads:[~2018-03-09 10:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09  4:22 [Qemu-devel] Apparently fpu/softfloat.c:1374 is reachable Michael Clark
2018-03-09 10:44 ` Peter Maydell [this message]
2018-03-09 11:17   ` Michael Clark
2018-03-09 11:29     ` Philippe Mathieu-Daudé
2018-03-09 11:56       ` Michael Clark
2018-03-09 12:09         ` [Qemu-devel] Apparently fpu/softfloat.c:1374 is reachable (-> binary images) Liviu Ionescu
2018-03-09 13:20         ` [Qemu-devel] Apparently fpu/softfloat.c:1374 is reachable Michael Clark
2018-03-09 11:34     ` Michael Clark
2018-03-09 21:49       ` Emilio G. Cota
2018-03-09 22:31         ` Palmer Dabbelt

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='CAFEAcA_rPkjEgNc=uyQ2C+at8Zs28YZVAkOLAZk17JaVyjxuNw@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=mjc@sifive.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 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.