From: "Steve Ellcey " <sellcey@imgtec.com>
To: <vapier@gentoo.org>, <gdb-patches@sourceware.org>
Subject: MIPS simulator is broken
Date: Fri, 08 Jan 2016 22:30:00 -0000 [thread overview]
Message-ID: <5f31ca78-325c-4c18-9abf-16de50bac964@BAMAIL02.ba.imgtec.org> (raw)
Mike,
Your December 26th change to the mips simulator has broken it, at least
for me. I am trying to compile and run a program with mips32r2 big-endian
and am using the mti32.ld linker script.
After your commit my attempts to run a 'hello world' program die with:
mips-core: 4 byte read to unmapped address 0xffffffff80020004 at 0xffffffff80020004
program stopped with signal 10 (User defined signal 1).
Any idea what is causing this?
Steve Ellcey
sellcey@imgtec.com
The commit that caused this is:
commit 26f8bf63bf36f9062a5cc1afacf71462a4abe0c8
Author: Mike Frysinger <vapier@gentoo.org>
Date: Sat Dec 26 11:35:03 2015 -0500
sim: mips: delete mmu stubs to move to common sim_{read,write}
The only unique thing about mip's sim_{read,write} helpers is the call to
address_translation on the incoming address. When we look closer at that
function though, we see it's just a stub that maps physical to virtual,
and the cache/return values are hardcoded. If we delete this function,
we can then collapse all the callers and drop the custom sim_{read,write}
logic entirely.
Some day we might want to add MMU support, but when we do, we'll want to
have the common layers handle things so all targets benefit.
next reply other threads:[~2016-01-08 22:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 22:30 Steve Ellcey [this message]
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
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=5f31ca78-325c-4c18-9abf-16de50bac964@BAMAIL02.ba.imgtec.org \
--to=sellcey@imgtec.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox