Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Steve Ellcey <sellcey@imgtec.com>, gdb-patches@sourceware.org
Subject: Re: MIPS simulator is broken
Date: Tue, 12 Jan 2016 06:49:00 -0000	[thread overview]
Message-ID: <20160112064923.GH4894@vapier.lan> (raw)
In-Reply-To: <20160112010025.GE4894@vapier.lan>

[-- Attachment #1: Type: text/plain, Size: 658 bytes --]

On 11 Jan 2016 20:00, Mike Frysinger wrote:
> i don't know why mips wants to do this, and considering literally no
> other target does it (ok, sh64 does it, but let's ignore them since
> that target is dead & being removed), it's probably not an accident.
> so we have to hack around it in the sim:

i've pushed that fix now

> that allows most tests to pass, but 6 (out of 69) are still failing.
> fpu64-ps.s for example has:
> mips-core: 8 byte read to unmapped address 0xffffffff80010b18 at 0x80010070

this one i punted to a bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=19447

someone who cares about the mips port will have to take a look
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-01-12  6:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08 22:30 Steve Ellcey 
2016-01-08 22:49 ` Mike Frysinger
2016-01-11 22:38   ` Steve Ellcey
2016-01-11 22:57     ` Mike Frysinger
2016-01-12  1:00 ` Mike Frysinger
2016-01-12  6:49   ` Mike Frysinger [this message]
2016-01-12 10:25   ` Pedro Alves
2016-01-30 16:10   ` Maciej W. Rozycki
2016-02-10  7:28     ` Mike Frysinger
2016-02-11 16:54       ` Maciej W. Rozycki
2016-03-10 14:09       ` Matthew Fortune
2016-03-21 11:54       ` Matthew Fortune
2016-04-05  8:33         ` Matthew Fortune

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=20160112064923.GH4894@vapier.lan \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=sellcey@imgtec.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