Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eric Christopher <echristo@redhat.com>
To: David Ung <davidu@mips.com>
Cc: Daniel Jacobowitz <drow@false.org>,
	binutils@sourceware.org, gdb-patches@sources.redhat.com
Subject: Re: [patch] MIPS16e support in simulator.
Date: Tue, 14 Jun 2005 17:40:00 -0000	[thread overview]
Message-ID: <1118770811.3242.11.camel@dzur.sfbay.redhat.com> (raw)
In-Reply-To: <1118747270.1621.757.camel@localhost.localdomain>


> > 
> > Looks like the jump instructions aren't executing the instructions in
> > the delay slot? See the definition of jalr in m16.igen.
> 
> This is correct.  The MIPS16e jrc, jalrc etc does not have a delay slot.
> 

OK. The docs I have don't call this out explicitly in the instruction
description and probably should given that other mips (and mips16)
instructions have delay slots.

> > 
> > I guess a good question would be asking how this patch was tested?
> > 
> > Otherwise it looks fine.
> 
> We've actually had MIPS16e simulator support for quite awhile at MIPS
> for our internal use.  We've been doing nightly regressions test on
> MIPS16e for gcc 3.4 and gdb for more that half year now.

You should say that sort of thing when you submit patches, e.g.:

"Tested on mips-elf using internal mips16e port. No regressions."

or some such.

-eric


  reply	other threads:[~2005-06-14 17:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-09 16:52 David Ung
2005-06-09 16:59 ` David Ung
2005-06-13  3:18 ` Daniel Jacobowitz
2005-06-13 17:03   ` Eric Christopher
2005-06-13 17:04     ` Daniel Jacobowitz
2005-06-13 23:22       ` Eric Christopher
2005-06-14 11:09         ` David Ung
2005-06-14 17:40           ` Eric Christopher [this message]
2005-06-14 17:51             ` Maciej W. Rozycki
2005-06-14 18:08               ` Eric Christopher
2005-06-14 17:48         ` Daniel Jacobowitz
2005-06-15 11:42           ` David Ung
2005-06-15 16:12 ` Andrew Cagney
2005-06-16 15:19   ` David Ung

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=1118770811.3242.11.camel@dzur.sfbay.redhat.com \
    --to=echristo@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=davidu@mips.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.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