From: Mike Frysinger <vapier@gentoo.org>
To: Steve Ellcey <sellcey@imgtec.com>
Cc: gdb-patches@sourceware.org
Subject: Re: MIPS simulator is broken
Date: Mon, 11 Jan 2016 22:57:00 -0000 [thread overview]
Message-ID: <20160111225707.GD4894@vapier.lan> (raw)
In-Reply-To: <1452551879.29343.112.camel@ubuntu-sellcey>
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
On 11 Jan 2016 14:37, Steve Ellcey wrote:
> On Fri, 2016-01-08 at 17:48 -0500, Mike Frysinger wrote:
> > On 08 Jan 2016 14:30, Steve Ellcey wrote:
> > > 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:
> >
> > please add a testcase to the sim/testsuite/ tree that triggers the error
> > when you run `make check`. i can look after that.
> > -mike
>
> I have no idea how to add a testcase to sim/testsuite but the mips
> tests that are already there all fail (they used to work). I built the
> mips-sde-elf toolchain (to see if it worked better than mips-mti-elf)
> and when I ran 'make check' in the sim directory all the existing mips
> tests failed on execution. I retested after backing out your change and
> everything passed.
they're all passing for me w/--target=mips-elf. i run `make check` for
all sim targets before i push changes, and especially when messing with
a single target.
but now you say you're using --target=mips-sde-elf, so i can check that.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-11 22:57 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 [this message]
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=20160111225707.GD4894@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